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 andrea.corbellini
Recipients andrea.corbellini, pitrou, ysj.ray
Date 2010-07-29.15:23:08
SpamBayes Score 0.005922956
Marked as misclassified No
Message-id <1280416991.32.0.0453801426135.issue9417@psf.upfronthosting.co.za>
In-reply-to
Content
Disabling the GC can increase performances (although not significantly). But this bug is the cause of other problems too: what if the metaclass contains a __del__() method?

An another issue that I've found is that debugging is harder. I always try to avoid to create ref cycles in my code, also if my objects are collectable. In this way, I'm sure that I'll always be able to add a __del__ method in the future without problems. However, I can't easily check ref cycles without manually inspecting `gc.garbage`.

And also, specifying DEBUG_SAVEALL will put all the deleted classes and their attributes in the garbage, which makes debugging *very* hard in case of a leaking program.
History
Date User Action Args
2010-07-29 15:23:11andrea.corbellinisetrecipients: + andrea.corbellini, pitrou, ysj.ray
2010-07-29 15:23:11andrea.corbellinisetmessageid: <1280416991.32.0.0453801426135.issue9417@psf.upfronthosting.co.za>
2010-07-29 15:23:09andrea.corbellinilinkissue9417 messages
2010-07-29 15:23:08andrea.corbellinicreate