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 josh.r
Recipients Denny Weinberg, Roman.Evstifeev, ammar2, belopolsky, josh.r, ncoghlan, palm.kevin
Date 2016-09-15.19:28:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hmm... On checking down some of the code paths and realizing there were some issues in 3.5 (redundant code, and what looked like two memory leaks), I checked tip (to avoid opening bugs on stale code), and discovered that #22557 rewrote the import code, reducing the cost of top level reimport by ~60%, so my microbenchmarks (run on Python 3.5.0) are already out of date for 3.6's faster re-import. Even so, caching wasn't a wholly unreasonable optimization before now, and undoing it now still has a cost, if a smaller one.
Date User Action Args
2016-09-15 19:28:36josh.rsetrecipients: + josh.r, ncoghlan, belopolsky, palm.kevin, Roman.Evstifeev, Denny Weinberg, ammar2
2016-09-15 19:28:36josh.rsetmessageid: <>
2016-09-15 19:28:36josh.rlinkissue27400 messages
2016-09-15 19:28:36josh.rcreate