[BUG] Py_TYPE and Py_REFCNT are used in limited api (3.11) #6853
Comments
|
I think this is a false positive from abi3audit. The status of the various macros in the limited API is really badly documented and they've been resistant to documenting it further (although I'm definitely not the only one that's been confused by it). But I believe they are in the Limited API and are OK to use. In Python 3.12 In Python 3.14 it gets changed into a non-static function which has to be linked to the definition in Python. So I think abi3audit is just seeing the static inline definition and misreporting it. If you try to use your library in Python 3.11 does it work? |
|
@da-woods You are right! It works fine despite the error coming from |
|
No problem. Thanks for trying out the limited API mode. Do report the issue to abi3audit if you haven't already. I'll close this issue since I think we're both convinced it's a false positive |
Describe the bug
I am trying to compile a wheel using the limited API feature of Cython 3.1 and when I use
abi3auditto check the built wheel, some symbols should have not been used. I am building the wheel for Python 3.11 stable ABI andabi3audithas found symbols that will be in the stable API for version 3.14 of Python.Code to reproduce the behaviour:
With this code, only
Py_TYPEappears in the built wheel. In my use case,Py_REFCNTalso appears.Expected behaviour
I would have expected my wheel to be compatible with the stable API of version 3.11.
OS
Linux
Python version
3.12.7
Cython version
3.1.0
Additional context
I am currently using the following compiler directives for building my wheel
The resulting
abi3auditcommand line and results:{ "specs": { "build/cy_test.abi3.so": { "kind": "object", "object": { "name": "cy_test.abi3.so", "result": { "is_abi3": true, "is_abi3_baseline_compatible": false, "baseline": "3.11", "computed": "3.14", "non_abi3_symbols": [], "future_abi3_objects": { "Py_TYPE": "3.14" } } } } } }The text was updated successfully, but these errors were encountered: