[3.14] gh-140061: Use _PyObject_IsUniquelyReferenced()
to check if objects are uniquely referenced (gh-140062)
#140157
+29
−36
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.
The previous
Py_REFCNT(x) == 1
checks can have data races in the freethreaded build.
_PyObject_IsUniquelyReferenced(x)
is a more conservativecheck that is safe in the free threaded build and is identical to
Py_REFCNT(x) == 1
in the default GIL-enabled build.(cherry picked from commit 32c2649)
Co-authored-by: Sergey Miryanov sergey.miryanov@gmail.com
Py_REFCNT(x) == 1
for free-threaded compatibility #140061