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 chris.jerdonek
Recipients chris.jerdonek, eric.araujo, ezio.melotti, terry.reedy
Date 2013-01-12.03:49:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357962546.75.0.213319951329.issue16927@psf.upfronthosting.co.za>
In-reply-to
Content
I admit that I'm used to the alphabetical listing, but I like the idea for this organization.  In fact, it's similar to how the Built-in Types page is organized: grouped by similarity rather than listed alphabetically.

Also just a note: strictly speaking there are built-in types not in the built-in types section (e.g. staticmethod and classmethod), but I think that's okay.  (There can be a disclaimer to this effect in the intro sentences of the first grouping.)

Lastly, it might also be worth grouping the built-in types into subgroups (similar to how they're done for Built-in Types).
History
Date User Action Args
2013-01-12 03:49:06chris.jerdoneksetrecipients: + chris.jerdonek, terry.reedy, ezio.melotti, eric.araujo
2013-01-12 03:49:06chris.jerdoneksetmessageid: <1357962546.75.0.213319951329.issue16927@psf.upfronthosting.co.za>
2013-01-12 03:49:06chris.jerdoneklinkissue16927 messages
2013-01-12 03:49:06chris.jerdonekcreate