Kaydet (Commit) 89c558da authored tarafından Georg Brandl's avatar Georg Brandl

Closes #22748: there are no PyString C functions in 3.x.

üst 01546a88
...@@ -43,10 +43,9 @@ separating others. ...@@ -43,10 +43,9 @@ separating others.
str/unicode Unification str/unicode Unification
----------------------- -----------------------
Python 3's :func:`str` type is equivalent to Python 2's :func:`unicode`; the C
Python 3's :func:`str` (``PyString_*`` functions in C) type is equivalent to functions are called ``PyUnicode_*`` for both. The old 8-bit string type has become
Python 2's :func:`unicode` (``PyUnicode_*``). The old 8-bit string type has :func:`bytes`, with C functions called ``PyBytes_*``. Python 2.6 and later provide a compatibility header,
become :func:`bytes`. Python 2.6 and later provide a compatibility header,
:file:`bytesobject.h`, mapping ``PyBytes`` names to ``PyString`` ones. For best :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 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 :c:type:`PyBytes` for binary data. It's also important to remember that
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment