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 michael.foord
Recipients alexgarel, chris.jerdonek, michael.foord, r.david.murray, rbcollins, slmnhq
Date 2012-04-21.14:19:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My favoured fix is to catch the exception and generate a failing test that re-raises the *original exception* (with traceback) when run. That way a single failing module doesn't kill a whole test run (although it does mean later feedback about misspelt imports). It also means (the main problem being reported here) that unittest no longer masks exceptions whilst importing test modules.

This would be a new feature / api change - so it would be Python 3.3 only (but it would go into unittest2).
Date User Action Args
2012-04-21 14:19:10michael.foordsetrecipients: + michael.foord, rbcollins, r.david.murray, slmnhq, chris.jerdonek, alexgarel
2012-04-21 14:19:10michael.foordsetmessageid: <>
2012-04-21 14:19:09michael.foordlinkissue7559 messages
2012-04-21 14:19:09michael.foordcreate