This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Date 2006-06-29.17:36:41
SpamBayes Score
Marked as misclassified
Logged In: YES 

So after staring at this crasher it seemed to me to be that
clearing the new weakrefs w/o calling their finalizers after
calling the object's finalizer was the best solution.  I
couldn't think of any other good way to communicate to the
new weakrefs that the object they refer to was no longer
viable memory without doing clear_weakref() work by hand.

Attached is a patch to do this.  Michael, can you have a look?
Date User Action Args
2007-08-23 14:36:35adminlinkissue1377858 messages
2007-08-23 14:36:35admincreate