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 benjamin.peterson, kristjan.jonsson, meador.inge, pitrou
Date 2012-04-16.21:59:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334613583.28.0.205766378539.issue8212@psf.upfronthosting.co.za>
In-reply-to
Content
__del__ methods are never invoked from GC.  All objects that have finalizers, and all objects reachable from them _must_ be put in gc.garbage.
If I'm not mistaken, this is a fundamental rule of python's gc module and it is not because of the unknown order of finalizers as some people seem to think, but because the state of the interpreter during the collection phase is so fragile, with objects being linked up in various lists, and so on, that it isn't permissable to run any dynamic code.
History
Date User Action Args
2012-04-16 21:59:43kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, benjamin.peterson, meador.inge
2012-04-16 21:59:43kristjan.jonssonsetmessageid: <1334613583.28.0.205766378539.issue8212@psf.upfronthosting.co.za>
2012-04-16 21:59:42kristjan.jonssonlinkissue8212 messages
2012-04-16 21:59:42kristjan.jonssoncreate