Re: Traceback not going all the way to the exception?

2008-10-09 Thread sert
sert <[EMAIL PROTECTED]> wrote in 
news:[EMAIL PROTECTED]:

> It's on Python 2.6.
> 

On Windows.
--
http://mail.python.org/mailman/listinfo/python-list


Re: Traceback not going all the way to the exception?

2008-10-09 Thread sert
Terry Reedy <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]: 

> You forgot to specify which version of Python on which
> computer system. 
> 

It's on Python 2.6.
--
http://mail.python.org/mailman/listinfo/python-list


Re: Traceback not going all the way to the exception?

2008-10-09 Thread Aaron "Castironpi" Brady
On Oct 9, 3:27 am, sert <[EMAIL PROTECTED]> wrote:
> I just got an exception and the traceback wouldn't go all the
> way to the statement that threw the exception. I found that out
> by using the debugger.
>
> Contrast the traceback:
>
> http://tinyurl.com/5xglde
>
> with the debugger output (notice the arrow pointing to the last
> statement the traceback showed and how the execution went on
> beyond it):
>
> http://tinyurl.com/3fjgrl
>
> Is this a known issue or should I submit a bug report?

Could be you are re-raising an exception by hand instead of with the
bare 'raise' statement.  Notice the difference in tracebacks shown
here:

>>> def f():
... try:
... g()
... except Exception, e:
... raise e
...
>>> def g():
... raise Exception("abc")
...
>>> f()
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 5, in f
Exception: abc
>>> def f():
... try:
... g()
... except Exception, e:
... raise
...
>>> f()
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 3, in f
  File "", line 2, in g
Exception: abc
>>>
--
http://mail.python.org/mailman/listinfo/python-list


Re: Traceback not going all the way to the exception?

2008-10-09 Thread Terry Reedy

sert wrote:
I just got an exception and the traceback wouldn't go all the 
way to the statement that threw the exception. I found that out 
by using the debugger.


Contrast the traceback:

http://tinyurl.com/5xglde

with the debugger output (notice the arrow pointing to the last 
statement the traceback showed and how the execution went on 
beyond it):


http://tinyurl.com/3fjgrl

Is this a known issue or should I submit a bug report?


You forgot to specify which version of Python on which computer system.
I do not remember anything like this.  You can search the items at 
bugs.python.org.  If no one explains this, I suggest a bug report.


--
http://mail.python.org/mailman/listinfo/python-list