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 r.david.murray
Recipients alexgarel, brett.cannon, chris.jerdonek, michael.foord, r.david.murray, rbcollins, slmnhq
Date 2012-06-03.14:36:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338734207.56.0.510289977067.issue7559@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for figuring that out.  And no, it doesn't matter if it is importlib.load_module or __import__, since both are provided by importlib now and both use the cache.

It's an interesting question where the cache clear should go.  I *think* it should go in the test, based on the idea that the cache is part of the environment, and therefore should be reset by tests that change what's on the path.  I'm not sure how we'd write an environment monitor for that, since not all changes to the import cache need to be reset.  I wonder if it would be worth putting a reset into DirsOnSysPath.
History
Date User Action Args
2012-06-03 14:36:47r.david.murraysetrecipients: + r.david.murray, brett.cannon, rbcollins, michael.foord, slmnhq, chris.jerdonek, alexgarel
2012-06-03 14:36:47r.david.murraysetmessageid: <1338734207.56.0.510289977067.issue7559@psf.upfronthosting.co.za>
2012-06-03 14:36:46r.david.murraylinkissue7559 messages
2012-06-03 14:36:46r.david.murraycreate