Author lemburg
Recipients Rhamphoryncus, ajaksu2, georg.brandl, lemburg, loewis
Date 2009-03-30.14:42:01
SpamBayes Score 1.47301e-07
Marked as misclassified No
Message-id <1238424123.29.0.426421612565.issue1581182@psf.upfronthosting.co.za>
In-reply-to
Content
See this talk for an explanation of the various Unicode terms and how
they map to Python's implementation:

http://www.egenix.com/library/presentations/#PythonAndUnicode

Also note that the Unicode standard has evolved a lot since Unicode
support was added to Python in late 1999. Some terms used in Python
differ from those used in Unicode 5.0 or have been defined in more
strict ways than were common at the time.

And finally: don't forget that Python provides ways of *working* with
Unicode, i.e. it does not guarantee that a Python Unicode string always
contains all code points required for e.g. UTF-16. It is well possible
to store lone surrogates and invalid or unassigned code points in a
Python Unicode string.
History
Date User Action Args
2009-03-30 14:42:03lemburgsetrecipients: + lemburg, loewis, georg.brandl, ajaksu2, rhamphoryncus.historic
2009-03-30 14:42:03lemburgsetmessageid: <1238424123.29.0.426421612565.issue1581182@psf.upfronthosting.co.za>
2009-03-30 14:42:01lemburglinkissue1581182 messages
2009-03-30 14:42:01lemburgcreate