[issue20296] PyArg_ParseTuple 2.X docs mention int for "t#", but "Py_ssize_t" for "w#", etc.

2020-05-31 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue20296] PyArg_ParseTuple 2.X docs mention int for t#, but Py_ssize_t for w#, etc.

2014-11-19 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- keywords: +easy stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20296 ___

[issue20296] PyArg_ParseTuple 2.X docs mention int for t#, but Py_ssize_t for w#, etc.

2014-11-19 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo, serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20296 ___ ___

[issue20296] PyArg_ParseTuple 2.X docs mention int for t#, but Py_ssize_t for w#, etc.

2014-01-18 Thread Rob Browning
New submission from Rob Browning: Here (http://docs.python.org/2/c-api/arg.html), the documentation for t# says: t# (read-only character buffer) [char *, int]... while the documentation for w# says: w# (read-write character buffer) [char *, Py_ssize_t]... However, from getargs.c, it