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, amaury.forgeotdarc, asvetlov, dstanek, kristjan.jonsson, loewis, pitrou, rhettinger, stutzbach, tim.peters
Date 2012-04-16.22:05:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334613952.18.0.205398524758.issue9141@psf.upfronthosting.co.za>
In-reply-to
Content
I've stumbled upon further cases of this problem, and a possible serious bug in python 3.
the _PyIOBase_finalize() will invoke a "close" method on the object if the object isn't closed.  This is the same as the object having a __del__ method.  Yet, these objects are not treated as having finalizers by the garbage collector, and indeed, _PyIOBase_finalize() is called by the tp_clear() slot of several derived types. Surely, if these objects define non-trivial 'close' members, they must not be called during garbage collection.
History
Date User Action Args
2012-04-16 22:05:52kristjan.jonssonsetrecipients: + kristjan.jonsson, tim.peters, loewis, rhettinger, amaury.forgeotdarc, pitrou, dstanek, stutzbach, asvetlov, Jim.Jewett
2012-04-16 22:05:52kristjan.jonssonsetmessageid: <1334613952.18.0.205398524758.issue9141@psf.upfronthosting.co.za>
2012-04-16 22:05:51kristjan.jonssonlinkissue9141 messages
2012-04-16 22:05:51kristjan.jonssoncreate