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 vstinner
Recipients ncoghlan, pitrou, vstinner
Date 2012-04-25.07:10:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwaUhyjjEZEoO8htKLQtd27YuZ0du9vp-x=prmm0w_F8GQ@mail.gmail.com>
In-reply-to <1335332949.45.0.352234246799.issue14665@psf.upfronthosting.co.za>
Content
> 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):

The output is something like:

Thread 0xf758d8d0:

 File "/home/edcjones/programs/python/Python-3.3.0a2/Lib/socket.py",
line 407 in create_connection
 File "/home/edcjones/programs/python/Python-3.3.0a2/Lib/imaplib.py",
line 236 in _create_socket
 File "/home/edcjones/programs/python/Python-3.3.0a2/Lib/imaplib.py",
line 1201 in _create_socket
...

"Thread 0xf758d8d0:" can be replaced with "Thread 0xf758d8d0 (most
recent call FIRST):".

A "reverse=False" parameter can be added to
faulthandler.dump_traceback() and
faulthandler.dump_tracebacks_later(). But I prefer to not add it to
faulthandler.enable() nor faulthandler.register() because
dump_traceback() is called from a signal handler. It may be surprising
to have an option on some functions but not on all functions.
History
Date User Action Args
2012-04-25 07:10:30vstinnersetrecipients: + vstinner, ncoghlan, pitrou
2012-04-25 07:10:29vstinnerlinkissue14665 messages
2012-04-25 07:10:29vstinnercreate