Adrien <delgan...@gmail.com> added the comment:
Thanks to your answer, @ned.deily. Sorry to insist, but are you sure this is a duplicate of issue18075 / issue35542? According to the discussion in issue36272, it seems this is not related to stack exhaustion nor to issue18075. Also, @remi.lapeyre suggested that a fix could be possible by modifying ceval.c. (re-raise RecursionError if it has been cleared). issue18075 and issue35542 are both of status "closed", I would expect this issue to be duplicate to an "open" issue because there is a clear reproducible "bug" which crashes the interpreter. There is also the problems still remaining in logging Handlers that I linked. I think this is an issue with how recursion error are handled in ceval.c, this is related to "tstate->overflowed" and "tstate->recursion_depth > recursion_limit + 50". If I understand correctly, this is implemented like this to allow gracefully catch and handle RecursionError from the calling function. For example, why not re-raise the exception if the first one could not be handled correctly? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37365> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
