➜

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 jcea
Recipients amaury.forgeotdarc, jcea, serhiy.storchaka, vstinner
Date 2012-11-10.02:38:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352515131.63.0.528538198309.issue16447@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes, we should add a "Py_REPLACE()" macro. Sure. +1 to that.

With this issue in mind, I wonder if there is any situation where "Py_DECREF/Py_XDECREF" must be used that can not be replace with "Py_CLEAR/Py_REPLACE".

Is there any code that breaks if we replace "Py_XDECREF()" by "Py_CLEAR()"?. Could be possible even to replace Py_DECREF definition?.
History
Date User Action Args
2012-11-10 02:38:51jceasetrecipients: + jcea, amaury.forgeotdarc, vstinner, serhiy.storchaka
2012-11-10 02:38:51jceasetmessageid: <1352515131.63.0.528538198309.issue16447@psf.upfronthosting.co.za>
2012-11-10 02:38:51jcealinkissue16447 messages
2012-11-10 02:38:51jceacreate