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.

classification
Title: Verify all imported modules at startup are needed
Type: resource usage Stage:
Components: Versions: Python 3.4
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: eric.snow, pitrou, vstinner
Priority: normal Keywords:

Created on 2012-10-01 16:47 by brett.cannon, last changed 2022-04-11 14:57 by admin.

Messages (3)
msg171733 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2012-10-01 16:47
It's probably time to examine what modules are imported at startup and whether they are necessary or if some can be trimmed off so as to avoid the overhead.
msg171761 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2012-10-01 23:29
See also issues #9548 and #14057.
msg171822 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012-10-02 18:39
These are not dependencies, though.
History
Date User Action Args
2022-04-11 14:57:36adminsetgithub: 60305
2020-01-29 00:39:05brett.cannonsetnosy: - brett.cannon
2013-01-09 13:09:44georg.brandllinkissue16908 superseder
2012-11-13 06:39:30eric.snowsetnosy: + eric.snow
2012-10-02 18:39:42pitrousetnosy: + pitrou
dependencies: - locale can be imported at startup but relies on too many library modules, Speedup sysconfig startup
messages: + msg171822
2012-10-02 13:08:14brett.cannonsetdependencies: + locale can be imported at startup but relies on too many library modules, Speedup sysconfig startup
2012-10-01 23:29:52vstinnersetnosy: + vstinner
messages: + msg171761
2012-10-01 16:47:08brett.cannoncreate