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 Jim.Jewett, Yury.Selivanov, asvetlov, ebfe, jimjjewett, kristjan.jonsson, lehmannro, michael.foord, pitrou, stutzbach
Date 2012-04-07.13:00:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333803609.82.0.595191178481.issue10576@psf.upfronthosting.co.za>
In-reply-to
Content
Here is an updated patch, taking Jim's and Antoine's comments into account.

Jim, I´d like to comment that I think the reason __del__ objects are uncollectable is more subtle than there being no defined order of calling the __del__ functions.  More significantly, no python code may be executed during an implicit garbage collection.
Now, it is possible that one could clean up cycles containing only one __del__ method during _expcicit_ collections (calling gc.collect()) but it hardly seems worth the effort.
History
Date User Action Args
2012-04-07 13:00:09kristjan.jonssonsetrecipients: + kristjan.jonsson, jimjjewett, pitrou, lehmannro, stutzbach, michael.foord, ebfe, asvetlov, Yury.Selivanov, Jim.Jewett
2012-04-07 13:00:09kristjan.jonssonsetmessageid: <1333803609.82.0.595191178481.issue10576@psf.upfronthosting.co.za>
2012-04-07 13:00:09kristjan.jonssonlinkissue10576 messages
2012-04-07 13:00:07kristjan.jonssoncreate