Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:
> So the exception state would only stay available
> within the function itself.
AFAIK That's what python does for caught exceptions.
--
resolution: -> invalid
status: open -> closed
___
Py
Stefan Behnel <[EMAIL PROTECTED]> added the comment:
Thanks a lot for the analysis. I was considering that this was a problem
with Cython, but since this was the first time I got a crash on this
(even Py3.0b1 didn't expose this), I wanted to ask here first.
Your explanation sounds like the right
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:
I reproduced the problem on Windows.
The exception shown is the AttributeError('next') raised and caught in
lxml._elementpath.find().
The "args" atribute is cleared in the BaseException_clear, during a call
to gc.collect() (in some tearD
New submission from Stefan Behnel <[EMAIL PROTECTED]>:
I get a reproducible crash under Linux when running the test cases of
lxml's trunk in Py3b2. As usual with these things, it's not reproducible
when running the crashing test by itself, only when it hits the test
during the usual test run (whi
