Marc-Andre Lemburg <m...@egenix.com> added the comment: STINNER Victor wrote: > > New submission from STINNER Victor <victor.stin...@haypocalc.com>: > > http://docs.python.org/py3k/c-api/arg.html is unclear about what is a > "string". > > Attached patch: > - Use directly bytes, bytearray and str types > - Replace "default encoding" by "``'utf-8'`` encoding" > - Add bytes and/or bytearray to "... buffer compatible object" because it's > not easy to understand what is a buffer compatible object, especially because > there are different kind of buffer objects: read-only, read-write, pinned, > etc. > - Fix reST syntax ("..note ::") > - Fix "es", "es#", "et" and "et#" formats: they doesn't accept "character > buffer compatible object" (can someone double check that?)
The character buffer concept is (unfortunately) gone in Python3. There's no way for a buffer compatible object to tell the arg parser that it is storing text data. Perhaps we can add something like that back via the Py_buffer flags for getting buffers. ---------- nosy: +lemburg title: Improve c-api/arg.rst: use "bytes" or "str" types instead of "string" -> Improve c-api/arg.rst: use "bytes" or "str" types instead of "string" _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8925> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
