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 berker.peksag, bethard, paul.j3, rhettinger, serhiy.storchaka, vstinner, wolma, yan12125
Date 2017-04-26.06:58:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493189910.14.0.665338073412.issue30152@psf.upfronthosting.co.za>
In-reply-to
Content
Please stop rearranging everything in the standard library.  Every day I look at the tracker and there is a new patch from this dev that alters dozens of files.  

Some parts of the patch are harmless but other parts needlessly 
constipates the code for very little benefit.  I would be embarrassed to have to explain why core developers think it is a best practice to move a heapq import inside a Counter method.  That isn't a PEP-8 recommended practice.  Ordinarily, we only recommend deferred imports in extreme cases where the resource might not be available at import time or when the import is *very* expensive.

In general, we've already committed too many sins in the name of optimizing start-up time.  Mostly, these are false improvements because many of the changes just defer imports that ultimately end-up being needed anyway.  As we make useful tools, we're going to want to use them in the standard library to make the code better, but that is going to entail greater inter-dependencies and cross-imports.  Trying to avoid these is a losing game.
History
Date User Action Args
2017-04-26 06:58:30rhettingersetrecipients: + rhettinger, bethard, vstinner, berker.peksag, paul.j3, serhiy.storchaka, wolma, yan12125
2017-04-26 06:58:30rhettingersetmessageid: <1493189910.14.0.665338073412.issue30152@psf.upfronthosting.co.za>
2017-04-26 06:58:30rhettingerlinkissue30152 messages
2017-04-26 06:58:29rhettingercreate