[Python-Dev] Provoking Jim's MRO segfault before shutdown

Tim Peters tim at zope.com
Tue Nov 18 11:39:36 EST 2003

[Barry Warsaw, from last week]
> When Python's shutting down, will there /be/ another GC invocation?

This doesn't appear to be an issue in the current version of the patch.
Nothing is systemically delayed until "the next" GC invocation anymore.
Weakref callbacks triggered *by* a weakref callback going away are
excruciatingly suppressed until near the end of a gc run under the patch,
but they're allowed to trigger before gc returns.  That may create more
cyclic trash, which won't be discovered before the next gc invocation, but
that would have been true even if the callbacks-on-callbacks hadn't been
temporarily suppressed (i.e., it was already that way).

More information about the Python-Dev mailing list