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, luiz.poleto, martin.panter, ncoghlan, r.david.murray
Date 2015-03-11.00:37:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Closely related: Issue 14285, where an ImportError and various other exceptions caused by code in are also incorrectly caught, trigger unexpected error messages, with no traceback being reported.

Not sure if checking the “name” attribute will help in even all of the most common cases, but it should be better than nothing. Another idea I had was checking if a module was inserted into sys.modules.
Date User Action Args
2015-03-11 00:37:56martin.pantersetrecipients: + martin.panter, ncoghlan, r.david.murray, eric.snow, Anthony.Kong, berker.peksag, Fotis.Koutoulakis, luiz.poleto
2015-03-11 00:37:55martin.pantersetmessageid: <>
2015-03-11 00:37:55martin.panterlinkissue19771 messages
2015-03-11 00:37:55martin.pantercreate