Amaury Forgeot d'Arc <amaur...@gmail.com> added the comment: Hmm, the interpreter should not crash so easily with pyre Python code. (The same code correctly raises RuntimeException wich python 2.x) The issue should be corrected IMO.
The exact behavior seem to depend on where the recursion limit is detected: - If it is detected at the beginning of the function (at the start of PyEval_EvalFrameEx) or before the "try" statement, the exception is correctly propagated and displayed. This case always happens with 2.x, and you get the same on 3.0 if you add for example str([[[[[[[[]]]]]]]]) at the beginning of the function. - The crash occurs when the recursion limit is detected while PyEval_EvalFrameEx calls PyErr_NormalizeException() (in the "why == WHY_EXCEPTION" block). This does not change the control flow: the original exception is simply replaced by the RuntimeError, and nested calls continue 50 more frames. Here is a tentative patch. ---------- keywords: +patch nosy: +amaury.forgeotdarc resolution: invalid -> status: closed -> open Added file: http://bugs.python.org/file13990/stackoverflow.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6028> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
