This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jim.Jewett
Recipients Jim.Jewett, Rosuav, docs@python, gvanrossum, ncoghlan, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2014-06-10.23:02:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think the new wording is an improvement, but keeping the changes minimal left it in an awkward in-between state.


A string is a sequence of Unicode code points.  Strings can include any sequence of code points, including some which are semantically meaningless, or explicitly undefined.

Python doesn't have a :c:type:`char` type; a single code point is represented as a string of length ``1``.  The built-in function :func:`chr` translates an integer in the range ``U+0000 - U+10FFFF`` to the corresponding length ``1`` string object, and :func:`ord` does the reverse.

:meth:`str.encode` provides a concrete representation (as :class:`bytes` in the given text encoding) suitable for transport and communication with non-Python utilities.  :meth:`bytes.decode` decodes such byte sequences into text strings.
Date User Action Args
2014-06-10 23:02:39Jim.Jewettsetrecipients: + Jim.Jewett, gvanrossum, ncoghlan, pitrou, vstinner, docs@python, python-dev, Rosuav, serhiy.storchaka
2014-06-10 23:02:39Jim.Jewettsetmessageid: <>
2014-06-10 23:02:39Jim.Jewettlinkissue21667 messages
2014-06-10 23:02:39Jim.Jewettcreate