GH-91079: Decouple C stack overflow checks from Python recursion checks. #96507
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Python recursion checks work as before.
In addition there is a separate counter for C stack checking which works as follows:
Py_CheckRecursiveCall()
use 1 point.PyObject_Repr
use 2 points as they seem to use a bit more stack than most functions._PyEval_EvalFrameDefault
use 3 points, as it is a big function and keeps the limit in line with the original limit of 1000Py_CheckRecursiveCall()
I intend to add PRs to perform real stack checks for the major platforms, but this seems to offer a reasonable approximation for other platforms.