➜

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 skrah
Recipients python-dev, rhettinger, serhiy.storchaka, skrah, vstinner
Date 2016-02-11.21:29:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455226188.89.0.805131548139.issue26200@psf.upfronthosting.co.za>
In-reply-to
Content 
As Serhiy mentioned, I'm really happy with the Py_SETREF() macro and I understand the reasons why it was applied so broadly.

But if a module maintainer prefers not to change existing (and
correct) code, then that should have priority (also, the existing
version was quite readable).
History
Date User Action Args
2016-02-11 21:29:48skrahsetrecipients: + skrah, rhettinger, vstinner, python-dev, serhiy.storchaka
2016-02-11 21:29:48skrahsetmessageid: <1455226188.89.0.805131548139.issue26200@psf.upfronthosting.co.za>
2016-02-11 21:29:48skrahlinkissue26200 messages
2016-02-11 21:29:48skrahcreate