Jeffrey Yasskin schrieb:
> This apparently happens because the traceback in sys.exc_info keeps
> the frame for the call to RunSelfFunction._run alive even though there
> are otherwise no references to the object. In 2.6, this is fixed by
> calling sys.exc_clear() before allowing the thread to be jo
> The explanation seems to be that, while exc_info is cleared immediately, the
> thread state exception fields are only cleaned up at the end of
> PyEval_EvalFrameEx.
Patch and test in http://bugs.python.org/issue2507
___
Python-3000 mailing list
Pyth
Hi Jeffrey,
> I had thought that exc_info was
> automatically cleared at the end of any except block that caught an
> exception, but apparently that isn't the case. Is this a bug in 3.0,
> or do we need to keep sys.exc_clear() around?
The explanation seems to be that, while exc_info is cleared i
If you apply the following patch to the py3k branch, you can watch
test_threading fail in test_no_refcycle_through_target:
Index: Lib/threading.py
===
--- Lib/threading.py(revision 62033)
+++ Lib/threading.py(working copy)
@@
