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 ncoghlan
Recipients brett.cannon, eric.snow, mjacob, ncoghlan
Date 2017-03-19.11:22:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489922558.59.0.581156276422.issue29830@psf.upfronthosting.co.za>
In-reply-to
Content
Right, there's a longstanding RFE to allow builtin packages and submodules: https://bugs.python.org/issue1644818

At the moment, modules like pyexpat are more like the os module than they are packages: they eagerly set other modules as attributes at import time (akin to os.path), rather than defining an actual package with submodules that can be optionally loaded via the import system.

Given the import system changes in recent 3.x releases, I'd expect it to be feasible (but not necessarily easy) to come up with a viable specification and implementation for builtin and extension packages that work similarly to traditional packages (perhaps based on the handling of frozen packages).
History
Date User Action Args
2017-03-19 11:22:38ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.snow, mjacob
2017-03-19 11:22:38ncoghlansetmessageid: <1489922558.59.0.581156276422.issue29830@psf.upfronthosting.co.za>
2017-03-19 11:22:38ncoghlanlinkissue29830 messages
2017-03-19 11:22:38ncoghlancreate