-
Notifications
You must be signed in to change notification settings - Fork 0
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
PEP about abi4 etc. (placeholder) #5
Comments
I have many ideas how what to put in an abi4. But when it comes to noGIL, I have one request: make PyObject structure empty. The PyObject members would be stored before
The main drawback is that currently,
I'm considering to write a first PEP only to make PyObject opaque: it doesn't imply to make PyObject empty, but only to prevent direct access to PyObject. IMO it's pre-requirement to be able to move PyObject members before |
Sam Gross (@colesbury) has an elaborate proposal for abi4. He's going to draft a PEP.
Things I recall:
PyObject_HEAD
to be 32 bytes (it's 16 bytes currently -- all on 64-bit platforms).Py_LIMITED_API
), the wheel's abi tag (abi3
orabi4
), the wheel's CPython version tag (e.g.cp312
), the CPython version used to build the extension, the CPython used to load the extension.The text was updated successfully, but these errors were encountered: