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 akuchling
Recipients akuchling, asvetlov, barry, docs@python, levkivskyi, yselivanov
Date 2018-05-29.00:35:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527554142.68.0.682650639539.issue33649@psf.upfronthosting.co.za>
In-reply-to
Content
The plan for updating things looks good, and I think the ordering of
tasks is good -- rearranging the APIs is a pretty simple first step,
and it matches other chapters in the Library Reference, which list
more important modules first and more specialized obscure modules
later.  Then we can work on writing the additional material.

Yury: do you want to do the re-organization into high- and low-level APIs?  If you'd like me to do it, I'll need a more explicit listing of which APIs fall into which category.  Also, do we want to create an explicit high-level and low-level sections and push everything else down a level, or just leave it implicit in the ordering?
History
Date User Action Args
2018-05-29 00:35:42akuchlingsetrecipients: + akuchling, barry, asvetlov, docs@python, yselivanov, levkivskyi
2018-05-29 00:35:42akuchlingsetmessageid: <1527554142.68.0.682650639539.issue33649@psf.upfronthosting.co.za>
2018-05-29 00:35:42akuchlinglinkissue33649 messages
2018-05-29 00:35:42akuchlingcreate