This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients chris.jerdonek, docs@python, eric.araujo, ezio.melotti, ncoghlan, terry.reedy
Date 2012-11-25.10:47:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353840442.45.0.713701045636.issue16209@psf.upfronthosting.co.za>
In-reply-to
Content
Right, aside from my recent revamp, much of the existing layout of the types section has been inherited from the pre-new style classes days when you *couldn't* inherit from types, and strings were the only one with a non-trivial number of methods.

Rearranging as Chris suggests makes sense to me - my work was certainly only intended to be the *start* of improvements to the builtin type docs.

The main thing to watch out for is ensuring we don't break any incoming deep links while rearranging things (perhaps by adding the appropriate explicit anchor targets). It's OK if some cases end up just linking to the page (e.g. that's what now happens to reference to the old monolithic sequence types section, as there's no obviously better destination), but in this case the old deep links should go to the new class docs.
History
Date User Action Args
2012-11-25 10:47:22ncoghlansetrecipients: + ncoghlan, terry.reedy, ezio.melotti, eric.araujo, chris.jerdonek, docs@python
2012-11-25 10:47:22ncoghlansetmessageid: <1353840442.45.0.713701045636.issue16209@psf.upfronthosting.co.za>
2012-11-25 10:47:22ncoghlanlinkissue16209 messages
2012-11-25 10:47:21ncoghlancreate