Message126460
It seems that tracing in the interpreter is lost after some recursion error is triggered (even if it's properly handled).
This breaks any debugger working after any recursion error is triggered (which suppose shouldn't happen).
The attached test case shows the problem in action.
Tested the problem with Python 2.6.5 and 3.1.3 |
|
Date |
User |
Action |
Args |
2011-01-18 12:31:13 | fabioz | set | recipients:
+ fabioz |
2011-01-18 12:31:12 | fabioz | set | messageid: <1295353872.95.0.129870258846.issue10933@psf.upfronthosting.co.za> |
2011-01-18 12:31:08 | fabioz | link | issue10933 messages |
2011-01-18 12:31:08 | fabioz | create | |
|