Message237829
Closely related: Issue 14285, where an ImportError and various other exceptions caused by code in __init__.py 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:56 | martin.panter | set | recipients:
+ martin.panter, ncoghlan, r.david.murray, eric.snow, Anthony.Kong, berker.peksag, Fotis.Koutoulakis, luiz.poleto |
2015-03-11 00:37:55 | martin.panter | set | messageid: <1426034275.95.0.944656620976.issue19771@psf.upfronthosting.co.za> |
2015-03-11 00:37:55 | martin.panter | link | issue19771 messages |
2015-03-11 00:37:55 | martin.panter | create | |
|