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 arigo
Recipients amaury.forgeotdarc, arigo, daniel.urban, fdrake, gvanrossum, isoschiz, kristjan.jonsson, ncoghlan, pconnell, pitrou
Date 2013-05-14.16:10:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368547802.63.0.27865581962.issue17950@psf.upfronthosting.co.za>
In-reply-to
Content
Well, adding weak references left and right to break cycles is going to subtly change or break people's code and hasn't been done so far, but that's only my opinion.  Anyway, I want to correct what you say about tp_subclasses: yes, tp_subclasses is a list of weakrefs, but the reason is not (as I think you mean) to avoid cycles.  The reason is simply that if it were strong references, then all classes ever created would stay alive.
History
Date User Action Args
2013-05-14 16:10:02arigosetrecipients: + arigo, gvanrossum, fdrake, amaury.forgeotdarc, ncoghlan, pitrou, kristjan.jonsson, daniel.urban, pconnell, isoschiz
2013-05-14 16:10:02arigosetmessageid: <1368547802.63.0.27865581962.issue17950@psf.upfronthosting.co.za>
2013-05-14 16:10:02arigolinkissue17950 messages
2013-05-14 16:10:02arigocreate