[Python-Dev] sys.last_traceback - annoying pdb behaviour
Alexander Schremmer
2007a at usenet.alexanderweb.de
Sat Aug 18 23:39:04 CEST 2007
Guido van Rossum wrote:
> On 8/18/07, Alexander Schremmer <2006a at usenet.alexanderweb.de> wrote:
>> when I tried to use pdb, I spotted some kind of annoying behaviour of
>> pdb: for pdb.pm, it still uses sys.last_traceback which is set by code.py
>>
>> This renders the function unusable in non-interactive contexts ... I
>> suggest to change pdb.pm to use sys.exc_traceback instead. Any reasons
>> not to do so?
> sys.last_traceback is the only place where you can reliably find the
> latest *uncaught* traceback. There is no intention to get rid of it in
> Py3k or to change this behavior. If you have another traceback you'd
> like to print, you can use pdb.post_mortem(sys.exc_info()[2]).
Indeed, I did not see that it is also set in pythonrun. How do you think
about changing pdb.pm to use exc_info if last_exception is not set?
Kind regards,
Alexander
More information about the Python-Dev
mailing list