summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-10-25 07:30:19 (GMT)
committerEzio Melotti <ezio.melotti@gmail.com>2011-10-25 07:30:19 (GMT)
commit7a03f64c2e6e417fda46c725867a5edad929a66e (patch)
treebe91a4f13bec0cfbec4a11af14ed0890d9f4bfde
parent90bf5f11713bbb3cf484e49a5cd9f0faecd86212 (diff)
downloadcpython-7a03f64c2e6e417fda46c725867a5edad929a66e.zip
cpython-7a03f64c2e6e417fda46c725867a5edad929a66e.tar.gz
cpython-7a03f64c2e6e417fda46c725867a5edad929a66e.tar.bz2
Remove mention of narrow/wide builds in the codecs doc.
-rw-r--r--Doc/library/codecs.rst8
1 files changed, 3 insertions, 5 deletions
diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst
index 2a7abf9..fe09e05 100644
--- a/Doc/library/codecs.rst
+++ b/Doc/library/codecs.rst
@@ -787,11 +787,9 @@ methods and attributes from the underlying stream.
Encodings and Unicode
---------------------
-Strings are stored internally as sequences of codepoints (to be precise
-as :c:type:`Py_UNICODE` arrays). Depending on the way Python is compiled (either
-via ``--without-wide-unicode`` or ``--with-wide-unicode``, with the
-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
+Strings are stored internally as sequences of codepoints in range ``0 - 10FFFF``
+(see :pep:`393` for more details about the implementation).
+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
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