[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Change by Gordon P. Hemsley : -- nosy: +gphemsley ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Fabio Zadrozny added the comment: Well, I'd say that if tracing is enabled and is disabled automatically by Python (thus breaking a working debugger which would usually be used to diagnose the error), I'd at least consider issuing some warning to stderr... (probably warnings.warn cannot be

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

R. David Murray added the comment: We also discussed whether or not it would be worth indicating in the exception that tracing has been disabled. I believe that implementing this would be aided by resolution of issue 23188. Doing a chained exception for this would also make it clearer that

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Peter McCormick added the comment: Removed unrelated doc changes. -- Added file: http://bugs.python.org/file38909/issue_10933-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10933 ___

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

James Powell added the comment: We investigated this issue with pdmccormick r.david.murray. The behaviour appears to be intentional. If the trace function raises an Exception, system tracing is disabled entirely. See attached documentation patch to clarify this. -- keywords: +patch

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Changes by James Powell ja...@dontusethiscode.com: -- nosy: +james, r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10933 ___ ___

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Changes by Peter McCormick pe...@pdmccormick.com: -- nosy: +pdmccormick ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10933 ___ ___

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

Mark Lawrence added the comment: Can we have a response to this please. -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.4, Python 3.5 -Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10933

[issue10933] Tracing disabled when a recursion error is triggered (even if properly handled)

New submission from Fabio Zadrozny fab...@users.sourceforge.net: 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).