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 martin.panter
Recipients Anthony.Kong, Fotis.Koutoulakis, berker.peksag, eric.snow, lac, luiz.poleto, martin.panter, ncoghlan, r.david.murray
Date 2015-12-11.05:00:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1449810031.69.0.457980776403.issue19771@psf.upfronthosting.co.za>
In-reply-to
Content
I think I have fixed the original problem via Issue 14285 (fully in 3.5+, partly in 2.7). It involved a bit more than checking ImportError.name, because runpy catches other exceptions like AttributeError, which do not identify a module name.

That leaves Laura’s error with the bad *.pyc file. I propose bad-pyc.patch, which adds the sys.modules check to fix the error message, and adds a test case. I think this patch should be applicable to Python 2 as well.
History
Date User Action Args
2015-12-11 05:00:31martin.pantersetrecipients: + martin.panter, ncoghlan, r.david.murray, eric.snow, Anthony.Kong, berker.peksag, Fotis.Koutoulakis, luiz.poleto, lac
2015-12-11 05:00:31martin.pantersetmessageid: <1449810031.69.0.457980776403.issue19771@psf.upfronthosting.co.za>
2015-12-11 05:00:31martin.panterlinkissue19771 messages
2015-12-11 05:00:31martin.pantercreate