Issue 10619: Failed module loading in test discovery loses traceback (original) (raw)

Issue10619

Created on 2010-12-04 00:14 by michael.foord, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg123308 - (view) Author: Michael Foord (michael.foord) * (Python committer) Date: 2010-12-04 00:14
If a test module fails to load during unittest test discovery (SyntaxError or other exception) then the error is reported during the test run. Due to the way the exception is re-raised the traceback is lost. Originally reported as unittest2 issue 29: https://code.google.com/p/unittest-ext/issues/detail?id=29
msg125204 - (view) Author: Michael Foord (michael.foord) * (Python committer) Date: 2011-01-03 17:47
This doesn't appear to be true on py3k (traceback.format_exc is used to preserve the original traceback). Need to check on Python 2.7.
msg125206 - (view) Author: Michael Foord (michael.foord) * (Python committer) Date: 2011-01-03 17:56
Same is true of Python 2.7 - looks like an invalid error report.
History
Date User Action Args
2022-04-11 14:57:09 admin set github: 54828
2011-01-03 17:56:38 michael.foord set status: open -> closedmessages: + resolution: not a bugstage: needs patch -> resolved
2011-01-03 17:47:43 michael.foord set messages: + versions: - Python 3.2
2010-12-04 00:32:11 eric.araujo set nosy: + eric.araujo
2010-12-04 00:14:23 michael.foord create