GeezerVison

@birkenfeld: Hi, do you recall why you considered to deprecated PyArg_Parse() when you documented the bytes() type in 2007?

cc @serhiy-storchaka @pitrou

It makes sense because METH_OLDARGS had been deprecated, and removed already.
Having two similar but slightly different unnecessary function confuse users (and other Python implementations.)

PyArg_Parse() is used with METH_O and can be used for parsing separate arguments in other functions (for example if argument can be parsed as "i" or "s"), because there is no other public API for some format units or it is less convenient. You can find many examples in the CPython code.

I believe that it is a useful function and should remain.

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?
https://docs.python.org/dev/c-api/arg.html#c.PyArg_Parse

@methane: What do you think?

I had read only the doc. If there are enough use case for PyArg_Parse, the doc should be updated and deprecation comment should be removed.

@methane:

I had read only the doc. If there are enough use case for PyArg_Parse, the doc should be updated and deprecation comment should be removed.

I rewrote PyArg_Parse() documentation. Would you mind to review the updated PR?

Just to leave my requested feedback, I don't remember anything about this specific function :)