[issue31983] Officially add Py_SETREF and Py_XSETREF

Serhiy Storchaka added the comment: Since there are objections, it is too early to make this a public C API. -- resolution: -> rejected stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue31983] Officially add Py_SETREF and Py_XSETREF

Raymond Hettinger added the comment: Adding my -1. My experience was that these macros impaired my ability to maintain the code and interfered with useful patterns like delaying all decrefs until an object was in a consistent state. While I know that name was

[issue31983] Officially add Py_SETREF and Py_XSETREF

Change by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list

[issue31983] Officially add Py_SETREF and Py_XSETREF

Serhiy Storchaka added the comment: Does anyone want to propose a patch? This is mainly a documentation issue. Needed documenting Py_SETREF and Py_XSETREF in Doc/c-api/refcounting.rst, adding entries in Doc/whatsnew/3.7.rst, and "Misc/NEWS.d/next/C API/", and

[issue31983] Officially add Py_SETREF and Py_XSETREF

Stefan Krah added the comment: Just adding +1. -- nosy: +skrah ___ Python tracker ___

[issue31983] Officially add Py_SETREF and Py_XSETREF

Change by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

[issue31983] Officially add Py_SETREF and Py_XSETREF

New submission from Serhiy Storchaka : Private macros Py_SETREF and Py_XSETREF were introduced in 3.6 and backported to all maintained versions for fixing bugs (see issue20440 and issue26200). They are helpful and used not only for the primary purpose, but also for