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 brett.cannon
Recipients Arfrever, Pathangi Jatinshravan, brett.cannon, eric.snow, martin.panter, ncoghlan, r.david.murray
Date 2015-10-11.14:58:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444575490.97.0.0360445156372.issue25372@psf.upfronthosting.co.za>
In-reply-to
Content
This is entirely on purpose as you're not meant to call load_module() if you want to import code programmatically; that's what importlib.import_module() is for. The load_module() method -- which is kind of deprecated thanks to exec_module() -- is there purely to initialize the module being imported, with everything else the responsibility of other parts of import. You should only be calling load_module/execx_module tonload a specific set of bytes and to bypass the import machinery entirely, in which case you have to manage any "extras" you want, like setting a submodule on a parent package.
History
Date User Action Args
2015-10-11 14:58:11brett.cannonsetrecipients: + brett.cannon, ncoghlan, Arfrever, r.david.murray, eric.snow, martin.panter, Pathangi Jatinshravan
2015-10-11 14:58:10brett.cannonsetmessageid: <1444575490.97.0.0360445156372.issue25372@psf.upfronthosting.co.za>
2015-10-11 14:58:10brett.cannonlinkissue25372 messages
2015-10-11 14:58:10brett.cannoncreate