[issue12535] Chained tracebacks are confusing because the first traceback is minimal
Terry J. Reedy
report at bugs.python.org
Fri Jul 15 21:48:45 CEST 2011
Terry J. Reedy <tjreedy at udel.edu> added the comment:
I agree with Nick's rationale for the current order, and also like his idea of indicating that the first traceback is truncated (which has not been completely obvious to me). Bike-shedding a bit, I would prefer something more like:
Truncated traceback of caught exception:
The '(most recent call last)' bit is nonsensical when only the most recent call is given.
----------
nosy: +terry.reedy
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12535>
_______________________________________
More information about the Python-bugs-list
mailing list