Avoid use of PyObject_DelAttr{,String} in Python 3.12 SABI builds
#1225
+10
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PyObject_DelAttr{,String}are part of the stable ABI starting only from Python 3.13. Thus, when building extensions targeting the stable ABI for Python 3.12, we should fall back to the earlierPyObject_SetAttr{,String}(obj, key, NULL)pattern.This should fix the
abi3auditfailures I observed in nicholasjng/nanobind-bazel#83.The implementation idea is based on the second paragraph of the https://docs.python.org/3/c-api/object.html#c.PyObject_SetAttrString doc.