This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients docs@python, eric.araujo, georg.brandl, lemburg, vstinner
Date 2010-06-07.21:43:41
SpamBayes Score 0.0059025
Marked as misclassified No
Message-id <4C0D680C.9070101@egenix.com>
In-reply-to <1275851035.31.0.736999556947.issue8925@psf.upfronthosting.co.za>
Content
STINNER Victor wrote:
> 
> New submission from STINNER Victor <victor.stinner@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.
History
Date User Action Args
2010-06-07 21:43:54lemburgsetrecipients: + lemburg, georg.brandl, vstinner, eric.araujo, docs@python
2010-06-07 21:43:42lemburglinkissue8925 messages
2010-06-07 21:43:41lemburgcreate