gh-126035: add missing whitespace to *Py_EnterRecursiveCall messages#126036
Conversation
|
The way to test it would be to just trigger the recursion error and then catch it with an |
Yes, that's what I wanted to find :') (I was a bit lazy here TBH).
I don't really want to. At least, it doesn't hurt to always add it. We could implicitly add the whitespace by using |
*Py_EnterRecursiveCall* usages*Py_EnterRecursiveCall messages
*Py_EnterRecursiveCall messages*Py_EnterRecursiveCall messages
ZeroIntensity
left a comment
There was a problem hiding this comment.
I wasn't actually able to trigger the RecursionError in either of these cases--the "while calling a Python object" beat it, so this might be dead code anyway. LGTM!
This comment was marked as outdated.
This comment was marked as outdated.
…essages (pythonGH-126036) (cherry picked from commit 19e93e2) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…essages (pythonGH-126036) (cherry picked from commit 19e93e2) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
GH-126058 is a backport of this pull request to the 3.13 branch. |
|
GH-126059 is a backport of this pull request to the 3.12 branch. |
I don't know how to test it easily though so if anyone knows, feel free to help me! (or we can just observe that all other occurrences are prefixing the message with a whitespace and be done).
Py_CheckRecursiveCall& co #126035