[issue9158] PyArg_ParseTuple y* documentation is incorrect

Terrence Cole added the comment: Awesome! Thanks, and sorry for communicating the problem so poorly initially. -- ___ Python tracker ___

[issue9158] PyArg_ParseTuple y* documentation is incorrect

STINNER Victor added the comment: Oh ok, sorry. Fixed in r82597 (3.x) and r82598 (3.1). -- resolution: invalid -> fixed ___ Python tracker ___ ___

[issue9158] PyArg_ParseTuple y* documentation is incorrect

Terrence Cole added the comment: @Victor: "y* and z* result is a Py_buffer" Correct, so why is z* documented as [Py_buffer] and y* documented as [Py_buffer*]? If I make 'buffer' from your example a Py_buffer*, as documented, then python puts writes sizeof(Py_buffer) bytes into a random spot

[issue9158] PyArg_ParseTuple y* documentation is incorrect

STINNER Victor added the comment: y* and z* result is a Py_buffer, but in C you have to pass a reference to the result variable using &result. Full example: static PyObject * getargs_y_star(PyObject *self, PyObject *args) { Py_buffer buffer; PyObject *bytes; if (!PyArg_ParseTuple(a

[issue9158] PyArg_ParseTuple y* documentation is incorrect

Changes by Ezio Melotti : -- nosy: +haypo stage: -> patch review type: crash -> feature request ___ Python tracker ___ ___ Python-bugs

[issue9158] PyArg_ParseTuple y* documentation is incorrect

New submission from Terrence Cole : The documented C type for y* should be [Py_buffer], not [Py_buffer *], as with the documentation for z* and the convention followed by the other types. I'm not sure what 'type' this issue should have. I've set it at 'crash' initially, since that's how the b