STINNER Victor added the comment:
> Didn't know that. Well if that's the case, then obviously there is no reason
> to work specifically on this conversion.
If people want to use Py_NewRef(), I suggest to do while modifying the code for
another reason. But not propose PRs just to use
Yonatan Goldschmidt added the comment:
> I don't see how Py_NewRef() or Py_XNewRef() is less error prone. In my
> experience, any change is more likely to introduce new bugs than leaving the
> code unchanged.
Agree that inserting changes opens a door to introducing bugs.
However, the "end
STINNER Victor added the comment:
> Following https://bugs.python.org/issue42262, I think it'd be nice to convert
> existing C code to use the more concise Py_NewRef() and Py_XNewRef() where
> possible. Increases readability and less bug prone.
In general, we don't accept changes which are
New submission from Yonatan Goldschmidt :
Following https://bugs.python.org/issue42262, I think it'd be nice to convert
existing C code to use the more concise Py_NewRef() and Py_XNewRef() where
possible. Increases readability and less bug prone.
Opening this new issue to track the
