Message 410788 - Python tracker

➜

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	petr.viktorin
Recipients	docs@python, iritkatriel, martin.panter, petr.viktorin, pitrou, serhiy.storchaka
Date	2022-01-17.14:16:19
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
This cannot be changed in 3.x, since the PyObject_DelAttr macro calls PyObject_SetAttr(..., NULL), and the macro is expanded in all extensions that use the stable ABI. (Technically, it would be possible to add a PyObject_SetAttr macro that would warn/fail, while keeping the PyObject_SetAttr function untouched, but that would be a pain to test/maintain.) The wording could be clarified to something like: "This behaviour is deprecated in favour of using PyObject_DelAttr(), but there are currently no plans to remove it."

This cannot be changed in 3.x, since the PyObject_DelAttr macro calls PyObject_SetAttr(..., NULL), and the macro is expanded in all extensions that use the stable ABI.
(Technically, it would be possible to add a PyObject_SetAttr *macro* that would warn/fail, while keeping the PyObject_SetAttr *function* untouched, but that would be a pain to test/maintain.) 

The wording could be clarified to something like: "This behaviour is deprecated in favour of using PyObject_DelAttr(), but there are currently no plans to remove it."

History
Date	User	Action	Args
2022-01-17 14:16:20	petr.viktorin	set	recipients: + petr.viktorin, pitrou, docs@python, martin.panter, serhiy.storchaka, iritkatriel
2022-01-17 14:16:19	petr.viktorin	set	messageid: <[email protected]>
2022-01-17 14:16:19	petr.viktorin	link	issue22039 messages
2022-01-17 14:16:19	petr.viktorin	create