NotificationsYou must be signed in to change notification settings
Fork33.3k
Star69.8k

[3.9] bpo-28737: Document when tp_dealloc should call PyObject_GC_UnTrack() (GH-29246)#29248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

ambv merged 1 commit intopython:3.9frommiss-islington:backport-35e1ff3-3.9

Oct 28, 2021

Merged

[3.9] bpo-28737: Document when tp_dealloc should call PyObject_GC_UnTrack() (GH-29246)#29248

ambv merged 1 commit intopython:3.9frommiss-islington:backport-35e1ff3-3.9

Oct 28, 2021

Conversation

Copy link

Contributor

miss-islington commentedOct 27, 2021•
edited by bedevere-bot
Loading

Objects that support garbage collection ("container" objects) should
call PyObject_GC_UnTrack() from their destructors before clearing any
fields which may point to other "container" objects.
(cherry picked from commit35e1ff3)

Co-authored-by: Sam Grosscolesbury@gmail.com

https://bugs.python.org/issue28737

bpo-28737: Document when tp_dealloc should call PyObject_GC_UnTrack() (…

b5c5dc9

…pythonGH-29246)Objects that support garbage collection ("container" objects) shouldcall PyObject_GC_UnTrack() from their destructors before clearing anyfields which may point to other "container" objects.(cherry picked from commit35e1ff3)Co-authored-by: Sam Gross <colesbury@gmail.com>