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 tim.peters
Recipients karzes, tim.peters
Date 2020-10-02.20:01:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601668897.19.0.735470715735.issue41912@roundup.psfhosted.org>
In-reply-to
Content
The docs are already clear about that you play with `setrecursionlimit()` at your own risk:

"""
Set the maximum depth of the Python interpreter stack to limit. This limit prevents infinite recursion from causing an overflow of the C stack and crashing Python.

The highest possible limit is platform-dependent. A user may need to set the limit higher when they have a program that requires deep recursion and a platform that supports a higher limit. This should be done with care, because a too-high limit can lead to a crash.
"""

If you see a crash instead of a `RecursionError` exception when you _don't_ shoot yourself in the foot this way, that might be interesting. But, as is, you're deliberately overriding a mechanism designed to prevent these kinds of crashes.
History
Date User Action Args
2020-10-02 20:01:37tim.peterssetrecipients: + tim.peters, karzes
2020-10-02 20:01:37tim.peterssetmessageid: <1601668897.19.0.735470715735.issue41912@roundup.psfhosted.org>
2020-10-02 20:01:37tim.peterslinkissue41912 messages
2020-10-02 20:01:36tim.peterscreate