Bug report

Bug description:

To my knowledge, one can use newer Python version (e.g. Python 3.13) to build C extensions forolder Python versions (e.g. 3.12) when targeting the stable ABI. This is accomplished by settingPy_LIMITED_API to a suitable number like0x030b0000, which simply disables all features beyond this cutoff.

If this understanding is correct, then I would like to report a bug:

Python 3.13 added an new C API function forPyObject_DelAttr(). In contrast, Python 3.12 realized this operation using a macro wrappingPyObject_SetAttr():

#define  PyObject_DelAttr(O, A) PyObject_SetAttr((O), (A), NULL)

This change is problematic: extensions built on 3.13 targeting 3.12 stable ABI will now call a function that does not exist on Python 3.12, and such extensions will fail to load with a linker error. The change to the new C API entry point should have been guarded with#ifdefs.

This issue also affectsPyObject_DelAttrString().

CPython versions tested on:

3.13

Operating systems tested on:

Linux

Linked PRs

• gh-134989: Implement PyObject_DelAttr() as a macro in the limited C API #135021
• [3.14] gh-134989: Implement PyObject_DelAttr() as a macro in the limited C API (GH-135021) #135133
• [3.13] gh-134989: Implement PyObject_DelAttr() as a macro in the limited C API (GH-135021) #135134
• gh-134989: Fix Py_RETURN_NONE in the limited C API #135165
• [3.14] gh-134989: Fix Py_RETURN_NONE in the limited C API (GH-135165) #135178
• [3.13] gh-134989: Fix Py_RETURN_NONE in the limited C API (GH-135165) #135182