[issue10840] pyarg_parsetuple docs and py_buffer

Antoine Pitrou added the comment: Done in 3.2 and 3.1. For 2.7 the structure of the doc page would lead to too much repetition IMO. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: -Python 2.7 ___ P

[issue10840] pyarg_parsetuple docs and py_buffer

STINNER Victor added the comment: 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

[issue10840] pyarg_parsetuple docs and py_buffer

STINNER Victor added the comment: See also #8215. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue10840] pyarg_parsetuple docs and py_buffer

STINNER Victor added the comment: See also #8991. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue10840] pyarg_parsetuple docs and py_buffer

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10840] pyarg_parsetuple docs and py_buffer

New submission from Antoine Pitrou : The docs for "s*" and friends should mention that contiguity of the buffer is automatically enforced. -- assignee: d...@python components: Documentation messages: 125488 nosy: d...@python, exarkun, mark.dickinson, pitrou priority: normal severity: no