traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove mention of narrow/wide builds in the codecs doc.

This commit is contained in:
Ezio Melotti 2011-10-25 10:30:19 +03:00
parent 90bf5f1171
commit 7a03f64c2e
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Doc/library/codecs.rst
View File

@ -787,11 +787,9 @@ methods and attributes from the underlying stream.
Encodings and Unicode Encodings and Unicode
--------------------- ---------------------
Strings are stored internally as sequences of codepoints (to be precise Strings are stored internally as sequences of codepoints in range ``0 - 10FFFF``
as :c:type:`Py_UNICODE` arrays). Depending on the way Python is compiled (either (see :pep:`393` for more details about the implementation).
via ``--without-wide-unicode`` or ``--with-wide-unicode``, with the Once a string object is used outside of CPU and memory, CPU endianness
former being the default) :c:type:`Py_UNICODE` is either a 16-bit or 32-bit data
type. Once a string object is used outside of CPU and memory, CPU endianness
and how these arrays are stored as bytes become an issue. Transforming a and how these arrays are stored as bytes become an issue. Transforming a
string object into a sequence of bytes is called encoding and recreating the string object into a sequence of bytes is called encoding and recreating the
string object from the sequence of bytes is known as decoding. There are many string object from the sequence of bytes is known as decoding. There are many