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 Arfrever, brett.cannon, eric.snow, ncoghlan
Date 2014-01-03.07:59:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388735996.78.0.797647745609.issue19944@psf.upfronthosting.co.za>
In-reply-to
Content
find_spec() is at package level because find_module() is and for no other good reason I'm aware of.  I'd be just fine with moving it to util.  I don't expect it to be used enough to warrant that top-level placement.

Regarding builtins.__import__(), I'm using it in the event that someone "installed" their own __import__() which gives a different result than import_module().  Thus the parent used by find_spec() will be the expected one.  I agree that comment about this would be good.
History
Date User Action Args
2014-01-03 07:59:56eric.snowsetrecipients: + eric.snow, brett.cannon, ncoghlan, Arfrever
2014-01-03 07:59:56eric.snowsetmessageid: <1388735996.78.0.797647745609.issue19944@psf.upfronthosting.co.za>
2014-01-03 07:59:56eric.snowlinkissue19944 messages
2014-01-03 07:59:56eric.snowcreate