Uh oh!
There was an error while loading. Please reload this page.
gh-105373: Remove PyArg_Parse() deprecation - #105394
Conversation
vstinner
commented
Jun 6, 2023
@birkenfeld: Hi, do you recall why you considered to deprecated PyArg_Parse() when you documented the |
methane
commented
Jun 6, 2023
It makes sense because |
serhiy-storchaka
commented
Jun 6, 2023
PyArg_Parse() is used with I believe that it is a useful function and should remain. |
vstinner
commented
Jun 6, 2023
Argument Clinic generates PyArg_Parse() calls for some function signatures. There are around 69 calls to PyArg_Parse() in the CPython code base, included 15 genereated by Argument Clinic. If we really want to get ride of it, we should be good citizen and start by cleaning our own code base. But here I agree with @serhiy-storchaka, this function is fine and should be kept. If there are use cases where others functions are more appropriated, maybe the doc should be enhanced? @methane: What do you think? |
methane
commented
Jun 7, 2023
I had read only the doc. If there are enough use case for |
There is no plan to deprecate PyArg_Parse(). The deprecation was added as a comment in the C API documentation in 2007 by commit 85eb8c1.
vstinner
commented
Jun 9, 2023
I rewrote PyArg_Parse() documentation. Would you mind to review the updated PR? |
birkenfeld
commented
Jun 11, 2023
Just to leave my requested feedback, I don't remember anything about this specific function :) |
There is no plan to deprecate PyArg_Parse().
The deprecation was added as a comment in the C API documentation in 2007 by commit 85eb8c1.
📚 Documentation preview 📚: https://cpython-previews--105394.org.readthedocs.build/