[issue14665] faulthandler prints tracebacks in reverse order
Nick Coghlan
report at bugs.python.org
Wed Apr 25 07:49:09 CEST 2012
Nick Coghlan <ncoghlan at gmail.com> added the comment:
Victor's argument makes sense to me. What I'd be inclined to do is shout at the reader a bit in the traceback header by making it:
Traceback (most recent call FIRST):
And put a comment in the source code with the gist of what Victor wrote above (i.e. internal state may be corrupted, we do the best we can with what we've got, and that means printing the traceback from the inside out)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14665>
_______________________________________
More information about the Python-bugs-list
mailing list