summaryrefslogtreecommitdiffstats
path: root/Objects/object_layout_313.gv
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2024-06-18 14:54:51 (GMT)
committerGitHub <noreply@github.com>2024-06-18 14:54:51 (GMT)
commit1ce59849610fe03beebcddfacb3d055a7074ef16 (patch)
tree1000c3c2e89c99a3a77dd19fa640f2ebc4998cc1 /Objects/object_layout_313.gv
parent4f4973d740839757e888c854a1994a64cb900d7b (diff)
downloadcpython-1ce59849610fe03beebcddfacb3d055a7074ef16.zip
cpython-1ce59849610fe03beebcddfacb3d055a7074ef16.tar.gz
cpython-1ce59849610fe03beebcddfacb3d055a7074ef16.tar.bz2
[3.13] gh-118789: Add `PyUnstable_Object_ClearWeakRefsNoCallbacks` (GH-118807) (#120695)
This exposes `PyUnstable_Object_ClearWeakRefsNoCallbacks` as an unstable C-API function to provide a thread-safe mechanism for clearing weakrefs without executing callbacks. Some C-API extensions need to clear weakrefs without calling callbacks, such as after running finalizers like we do in subtype_dealloc. Previously they could use `_PyWeakref_ClearRef` on each weakref, but that's not thread-safe in the free-threaded build. (cherry picked from commit e8752d7b80775ec2a348cd4bf38cbe26a4a07615) Co-authored-by: Sam Gross <colesbury@gmail.com> Co-authored-by: Petr Viktorin <encukou@gmail.com>
Diffstat (limited to 'Objects/object_layout_313.gv')
0 files changed, 0 insertions, 0 deletions