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 rhettinger
Recipients adelfino, docs@python, rhettinger
Date 2018-07-16.09:53:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531734806.94.0.56676864532.issue34116@psf.upfronthosting.co.za>
In-reply-to
Content
I disagree that this would be an improvement.  The current organization has worked well for us.  In particular, some of the these types sometimes used like functions that produce a type (this is where the builtin functions docs do a good job).  In the stdtypes docs, we go into detail about what the types do and have them grouped in a way that can be compared and contrasted.

As a Python instructor, I ask newcomers to read the built-in functions section because it tells them a lot of what they need to know to get up and running with the language (indeed, that is why these are all builitins rather than relegated to modules).  The stdtypes section is more voluminous and rarely read start to finish (mostly just used as a reference).
History
Date User Action Args
2018-07-16 09:53:27rhettingersetrecipients: + rhettinger, docs@python, adelfino
2018-07-16 09:53:26rhettingersetmessageid: <1531734806.94.0.56676864532.issue34116@psf.upfronthosting.co.za>
2018-07-16 09:53:26rhettingerlinkissue34116 messages
2018-07-16 09:53:26rhettingercreate