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, pitrou
Date 2012-04-15.14:12:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334499172.75.0.479925006706.issue8212@psf.upfronthosting.co.za>
In-reply-to
Content
Another, less hacky but more intrusive, way would be to change the signature of tp_dealloc in a backwards compatible way:
typedef void (*destructor)(PyObject *, int *destroyed);

The destructor can then set the flag pointed to by 'destroyed' to 1 or 0, depending on whether actual destruction took place.  The caller will set the flag to '1' by default.

We could then change all internal destructors to conform, and know that external destructors will continue to work in the old way.
History
Date User Action Args
2012-04-15 14:12:52kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, benjamin.peterson
2012-04-15 14:12:52kristjan.jonssonsetmessageid: <1334499172.75.0.479925006706.issue8212@psf.upfronthosting.co.za>
2012-04-15 14:12:52kristjan.jonssonlinkissue8212 messages
2012-04-15 14:12:52kristjan.jonssoncreate