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 eric.snow
Recipients barry, brett.cannon, christian.heimes, eric.snow, pitrou, r.david.murray, vstinner
Date 2013-10-10.22:11:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381443084.91.0.506031124316.issue19216@psf.upfronthosting.co.za>
In-reply-to
Content
With ModuleSpec (PEP 451), the finder creates the spec object (where it stores the loader).  At that point the finder is free to store any stat object you like in spec.loader_state.  The spec is made available to the loader during exec (if the loader supports it, which the importlib loaders will).  So there is no need to add anything to any loader __init__.

The only catch is the slim possibility that the stat object will be stale by the time it gets used.  I seem to remember a case where something like this happened (related to distros building their system Python or something).
History
Date User Action Args
2013-10-10 22:11:24eric.snowsetrecipients: + eric.snow, barry, brett.cannon, pitrou, vstinner, christian.heimes, r.david.murray
2013-10-10 22:11:24eric.snowsetmessageid: <1381443084.91.0.506031124316.issue19216@psf.upfronthosting.co.za>
2013-10-10 22:11:24eric.snowlinkissue19216 messages
2013-10-10 22:11:24eric.snowcreate