From: Georg Brandl Date: Tue, 28 Oct 2014 20:38:49 +0000 (+0100) Subject: Closes #22748: there are no PyString C functions in 3.x. X-Git-Tag: v3.5.0a1~602^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=89c558da00dbf4237d9369764213fa5d6b0b8a50;p=python Closes #22748: there are no PyString C functions in 3.x. --- diff --git a/Doc/howto/cporting.rst b/Doc/howto/cporting.rst index 1ad77d687e..6ebcc4164d 100644 --- a/Doc/howto/cporting.rst +++ b/Doc/howto/cporting.rst @@ -43,10 +43,9 @@ separating others. str/unicode Unification ----------------------- - -Python 3's :func:`str` (``PyString_*`` functions in C) type is equivalent to -Python 2's :func:`unicode` (``PyUnicode_*``). The old 8-bit string type has -become :func:`bytes`. Python 2.6 and later provide a compatibility header, +Python 3's :func:`str` type is equivalent to Python 2's :func:`unicode`; the C +functions are called ``PyUnicode_*`` for both. The old 8-bit string type has become +:func:`bytes`, with C functions called ``PyBytes_*``. Python 2.6 and later provide a compatibility header, :file:`bytesobject.h`, mapping ``PyBytes`` names to ``PyString`` ones. For best compatibility with Python 3, :c:type:`PyUnicode` should be used for textual data and :c:type:`PyBytes` for binary data. It's also important to remember that