aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2013-10-29 08:16:56 +0100
committerGeorg Brandl <georg@python.org>2013-10-29 08:16:56 +0100
commit3d596fa90b3c862eb2c0fb67aaf42cf1237c3258 (patch)
tree095308640b340cbecaf2ed9b8f9732ad697d9237 /Doc/howto/unicode.rst
parentCloses #19416: fix references in the nntplib docs. (diff)
downloadcpython-3d596fa90b3c862eb2c0fb67aaf42cf1237c3258.tar.gz
cpython-3d596fa90b3c862eb2c0fb67aaf42cf1237c3258.tar.bz2
cpython-3d596fa90b3c862eb2c0fb67aaf42cf1237c3258.zip
Clarify sentence.
Diffstat (limited to 'Doc/howto/unicode.rst')
-rw-r--r--Doc/howto/unicode.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/unicode.rst b/Doc/howto/unicode.rst
index 2920aa11cb3..9d48a787e85 100644
--- a/Doc/howto/unicode.rst
+++ b/Doc/howto/unicode.rst
@@ -514,7 +514,7 @@ columns and can return Unicode values from an SQL query.
Unicode data is usually converted to a particular encoding before it gets
written to disk or sent over a socket. It's possible to do all the work
-yourself: open a file, read an 8-bit bytes object from it, and convert the string
+yourself: open a file, read an 8-bit bytes object from it, and convert the bytes
with ``bytes.decode(encoding)``. However, the manual approach is not recommended.
One problem is the multi-byte nature of encodings; one Unicode character can be