[Python-Dev] [Python-checkins] r87505 - in python/branches/py3k: Doc/c-api/unicode.rst Include/unicodeobject.h
R. David Murray
rdmurray at bitdance.com
Tue Dec 28 05:13:40 CET 2010
On Mon, 27 Dec 2010 02:49:29 +0100, victor.stinner <python-checkins at python.org> wrote:
> Author: victor.stinner
> Date: Mon Dec 27 02:49:29 2010
> New Revision: 87505
>
> Log:
> Issue #9738: document encodings of unicode functions
>
> Modified:
> python/branches/py3k/Doc/c-api/unicode.rst
> python/branches/py3k/Include/unicodeobject.h
>
> Modified: python/branches/py3k/Doc/c-api/unicode.rst
> ==============================================================================
> --- python/branches/py3k/Doc/c-api/unicode.rst (original)
> +++ python/branches/py3k/Doc/c-api/unicode.rst Mon Dec 27 02:49:29 2010
> @@ -1063,7 +1063,8 @@
> .. c:function:: int PyUnicode_CompareWithASCIIString(PyObject *uni, char *string)
>
> Compare a unicode object, *uni*, with *string* and return -1, 0, 1 for less
> - than, equal, and greater than, respectively.
> + than, equal, and greater than, respectively. *string* is an ASCII-encoded
> + string (it is interpreted as ISO-8859-1).
Does it mean anything to say that an ASCII string is interpreted as
ISO-8859-1? If it is ASCII-encoded it shouldn't have any bytes with
the 8th bit set, leaving no room for interpretation. So presumably
you mean it is (treated as) an ISO-8859-1 encoded string, despite the
function name?
--
R. David Murray www.bitdance.com
More information about the Python-Dev
mailing list