-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-134989: Fix Py_RETURN_NONE in the limited C API #135165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Fix Py_RETURN_NONE, Py_RETURN_TRUE and Py_RETURN_FALSE macros in the limited C API 3.11 and older: don't treat Py_None, Py_True and Py_False as immortal.
Thank you! |
Sorry, @vstinner and @encukou, I could not cleanly backport this to
|
GH-135178 is a backport of this pull request to the 3.14 branch. |
…#135178) gh-134989: Fix Py_RETURN_NONE in the limited C API (GH-135165) Fix Py_RETURN_NONE, Py_RETURN_TRUE and Py_RETURN_FALSE macros in the limited C API 3.11 and older: Don't treat Py_None, Py_True and Py_False as immortal. (cherry picked from commit 9258f3d) Co-authored-by: Victor Stinner <vstinner@python.org>
|
|
GH-135182 is a backport of this pull request to the 3.13 branch. |
|
Fix Py_RETURN_NONE, Py_RETURN_TRUE and Py_RETURN_FALSE macros in the limited C API 3.11 and older: don't treat Py_None, Py_True and Py_False as immortal.
PyObject_DelAttr[String]
in stable ABI builds targeting older CPython versions #134989