Issue 10840: pyarg_parsetuple docs and py_buffer (original) (raw)

Issue10840

Created on 2011-01-06 00:32 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg125488 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2011-01-06 00:32
The docs for "s*" and friends should mention that contiguity of the buffer is automatically enforced.
msg125489 - (view)	Author: STINNER Victor (vstinner) *	Date: 2011-01-06 00:35
See also #8991.
msg125490 - (view)	Author: STINNER Victor (vstinner) *	Date: 2011-01-06 00:36
See also #8215.
msg125491 - (view)	Author: STINNER Victor (vstinner) *	Date: 2011-01-06 00:44
Ah ok, now I remember the story. I cleaned up getargs.c recently. r83197 (#8991) removes the support of discontinious buffers. I guess that most developers don't know what a discontinious buffer is and so they don't support this kind of buffer. Moreover, most PyArg_Parse*() formats don't provide information about the buffer (how it is stored in memory), and so the caller cannot handle discontinious anyway. I think that even Python code developers don't know what a discontinious buffer is... I think that today there is just no program or library using Python discontinious buffer. And maybe the authors of the PEP forgot it too :-)
msg125514 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2011-01-06 07:21
Done in 3.2 and 3.1. For 2.7 the structure of the doc page would lead to too much repetition IMO.