This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fabioz
Recipients fabioz
Date 2011-01-18.12:31:08
SpamBayes Score 5.8885075e-07
Marked as misclassified No
Message-id <1295353872.95.0.129870258846.issue10933@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2011-01-18 12:31:13fabiozsetrecipients: + fabioz
2011-01-18 12:31:12fabiozsetmessageid: <1295353872.95.0.129870258846.issue10933@psf.upfronthosting.co.za>
2011-01-18 12:31:08fabiozlinkissue10933 messages
2011-01-18 12:31:08fabiozcreate