[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2021-12-29 Thread Irit Katriel
Irit Katriel added the comment: This was created about 10 years ago, I wonder if people still feel there is a need to change something here, or did we all get used to the status quo by now? In particular, the suggestion is to indicate that the traceback of chained exceptions is truncated.

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2020-11-04 Thread Irit Katriel
Change by Irit Katriel : -- versions: +Python 3.10, Python 3.9 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2013-05-10 Thread Raymond Hettinger
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___ ___

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2013-05-07 Thread Nick Coghlan
Nick Coghlan added the comment: Marking this as Library as well, since the traceback module should also be updated. -- components: +Library (Lib) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2013-04-23 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___ ___

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2013-04-19 Thread Martin Morrison
Changes by Martin Morrison m...@ensoft.co.uk: -- nosy: +isoschiz ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___ ___ Python-bugs-list

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2013-04-19 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- type: behavior - enhancement versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2012-07-04 Thread Nick Coghlan
Nick Coghlan ncogh...@gmail.com added the comment: I've thought of a different approach to this which should be less hazardous to doctests: include the truncation warning in the *traceback* section, rather than in the header. doctests already ignore the details of that section because

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-19 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___ ___ Python-bugs-list

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-16 Thread Nick Coghlan
Nick Coghlan ncogh...@gmail.com added the comment: The redundancy of the (most recent call last) when there's only one frame in the stack is a separate problem (as it happens even for unchained tracebacks), but feel free to create a new issue if you'd like to see it changed (I expect it would

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-15 Thread Terry J. Reedy
Terry J. Reedy tjre...@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

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-12 Thread Nick Coghlan
Nick Coghlan ncogh...@gmail.com added the comment: The ordering is as it is so that the last line in the displayed traceback corresponds to the exception that was actually caught. That is, the last line remains the same regardless of whether or not there was an earlier exception in the chain.

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-11 Thread R. David Murray
New submission from R. David Murray rdmur...@bitdance.com: Consider the following traceback: Traceback (most recent call last): File /home/rdmurray/python/email6/Lib/email/message.py, line 466, in __getattr__ return getattr(self._headers, key) AttributeError: '_Header_List' object has no

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-11 Thread Eric Snow
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +ericsnow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535 ___ ___ Python-bugs-list

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-11 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: I think the reason the chained tracebacks look backward to me is twofold: I'm used to the last one in the list being the *only* one I get (in python2), and the last one in the list is often the one I want to deal with first. This is

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-11 Thread Benjamin Peterson
Benjamin Peterson benja...@python.org added the comment: There _is_ no full traceback for the first exception. It stops as soon as it's handled. -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12535

[issue12535] Chained tracebacks are confusing because the first traceback is minimal

2011-07-11 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: One can argue that it is necessary to read the traceback in reverse order, so that reading the chain in reverse order is a logical extension of that. So I guess I have no serious objection to this being rejected. --