-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!
Check out: eBank.nz (Art Generator) |
Netwrck.com (AI Tools) |
Text-Generator.io (AI API) |
BitBank.nz (Crypto AI) |
ReadingTime (Kids Reading) |
RewordGame |
BigMultiplayerChess |
WebFiddle |
How.nz |
Helix AI Assistant
Conversation
cc @encukou |
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.
Thanks @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Thanks @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Thank you! |
Sorry, @encukou, I could not cleanly backport this to
|
|
|
|
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