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 brett.cannon
Recipients brett.cannon, mark.dickinson, ncoghlan
Date 2010-05-05.18:52:53
SpamBayes Score 0.0006276844
Marked as misclassified No
Message-id <1273085576.08.0.986483904898.issue8627@psf.upfronthosting.co.za>
In-reply-to
Content
I just came across the warning myself (after ignoring all the PyType_INIT() warnings; what to do about those?) and came to the same conclusion: it's a pain to fix.

One option is to do a PyErr_Occurred() check at inherit_slots() call sites. Would that mitigate the leak? If I remember correctly inherit_slots() is not called constantly (only when a type is being created?) so having the expensive PyErr_Occurred() call should not hurt performance.
History
Date User Action Args
2010-05-05 18:52:56brett.cannonsetrecipients: + brett.cannon, mark.dickinson, ncoghlan
2010-05-05 18:52:56brett.cannonsetmessageid: <1273085576.08.0.986483904898.issue8627@psf.upfronthosting.co.za>
2010-05-05 18:52:53brett.cannonlinkissue8627 messages
2010-05-05 18:52:53brett.cannoncreate