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 Arfrever, brett.cannon, eric.snow, ncoghlan
Date 2014-12-12.06:29:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418365783.02.0.42403222524.issue23014@psf.upfronthosting.co.za>
In-reply-to
Content
Sounds good to me.

I'm not sure what to put in the docs about calling importlib.util.module_from_spec() from create_module() implementations. Really, if a loader can use that, then it should be doing whatever it was going to do after the call in exec_module() instead.

create_module() is intended specifically for cases where you genuinely need to do something different to create the object (as in the concept of calling in to a C level module creation hook, or the idea of allowing a __new__.py file in package directories)
History
Date User Action Args
2014-12-12 06:29:43ncoghlansetrecipients: + ncoghlan, brett.cannon, Arfrever, eric.snow
2014-12-12 06:29:43ncoghlansetmessageid: <1418365783.02.0.42403222524.issue23014@psf.upfronthosting.co.za>
2014-12-12 06:29:43ncoghlanlinkissue23014 messages
2014-12-12 06:29:42ncoghlancreate