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 taleinat
Recipients Julian.Gindi, Tim.Graham, berker.peksag, bignose, brett.cannon, davidszotten@gmail.com, eric.snow, ezio.melotti, ncoghlan, python-dev, rhettinger, serhiy.storchaka, taleinat
Date 2017-10-25.13:47:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508939263.46.0.213398074469.issue21720@psf.upfronthosting.co.za>
In-reply-to
Content
I can't say I agree that the performance here is practically insignificant. This will affect the startup time of Python process, and adding even 10% to that in some cases is significant.

In some of the larger codebases I've worked on, even simple scripts would import large portions of the system, and there would be thousands of such imports done in the process. There are "basic" utilities in the stdlib which are imported very often in different modules, so the performance of the import statement is not necessarily insignificant compared to that of actually loading the modules.

That being said I'm all for getting this in and implementing an optimization of the slower path in time for 3.7.
History
Date User Action Args
2017-10-25 13:47:43taleinatsetrecipients: + taleinat, brett.cannon, rhettinger, ncoghlan, ezio.melotti, bignose, python-dev, eric.snow, berker.peksag, serhiy.storchaka, Julian.Gindi, davidszotten@gmail.com, Tim.Graham
2017-10-25 13:47:43taleinatsetmessageid: <1508939263.46.0.213398074469.issue21720@psf.upfronthosting.co.za>
2017-10-25 13:47:43taleinatlinkissue21720 messages
2017-10-25 13:47:43taleinatcreate