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 kristjan.jonsson
Recipients kristjan.jonsson, pitrou, vstinner
Date 2013-05-13.10:15:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368440129.21.0.9865725643.issue17936@psf.upfronthosting.co.za>
In-reply-to
Content
Basically the logic is this:  When the class goes away, it _always_ calls remove_subclass().  Now, this may be before or after the weakref has been clear so that it will either find itself in a weakref, or a clear weakref.

In case this logic is flawed, we know that when remove_subclass() is called, exactly one child is removed.  Whether it is us, or some previous class, is irrelevant.
History
Date User Action Args
2013-05-13 10:15:29kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, vstinner
2013-05-13 10:15:29kristjan.jonssonsetmessageid: <1368440129.21.0.9865725643.issue17936@psf.upfronthosting.co.za>
2013-05-13 10:15:29kristjan.jonssonlinkissue17936 messages
2013-05-13 10:15:29kristjan.jonssoncreate