Re: [Python-Dev] sys.last_traceback - annoying pdb behaviour

2007-08-18 Thread Guido van Rossum
On 8/18/07, Alexander Schremmer <[EMAIL PROTECTED]> wrote: > 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? That would just confuse you if you're counting on that behavior, and then some time later last

Re: [Python-Dev] sys.last_traceback - annoying pdb behaviour

2007-08-18 Thread Alexander Schremmer
Guido van Rossum wrote: > On 8/18/07, Alexander Schremmer <[EMAIL PROTECTED]> 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 co

Re: [Python-Dev] sys.last_traceback - annoying pdb behaviour

2007-08-18 Thread Guido van Rossum
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]). On 8/18/07, Alexander Schr