[issue43048] Printing RecursionError results in RecursionError
Vladimir Feinberg
report at bugs.python.org
Mon Feb 1 20:28:38 EST 2021
Vladimir Feinberg <vlad at sisudata.com> added the comment:
Oh, yes, I suppose, that'll truncate to just the first TracebackException.
On Mon, Feb 1, 2021 at 4:38 PM Irit Katriel <report at bugs.python.org> wrote:
>
> Irit Katriel <iritkatriel at yahoo.com> added the comment:
>
> I meant to catch the exception in the constructor’s recursive call, and if
> necessary then the same again in format (if there are more function calls
> per exception in format, it will be necessary. The unit test from the 3.10
> patch will tell).
>
> Would that not work?
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue43048>
> _______________________________________
>
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue43048>
_______________________________________
More information about the Python-bugs-list
mailing list