Message410788
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." |
|
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: <1642428979.99.0.610127910325.issue22039@roundup.psfhosted.org> |
2022-01-17 14:16:19 | petr.viktorin | link | issue22039 messages |
2022-01-17 14:16:19 | petr.viktorin | create | |
|