Raymond Hettinger writes: > The naming convention for codecs is that the UTF prefix is used for > lossless encodings that cover the entire range of Unicode.
Sure. The operative word here is "codec", not "str", though. > "The first amendment to the original edition of the UCS defined > UTF-16, an extension of UCS-2, to represent code points outside the > BMP." Since when can s[0] represent a code point outside the BMP, for s a Unicode string in a narrow build? Remember, the UCS-2/narrow vs. UCS-4/wide distinction is *not* about what Python supports vs. the outside world. It's about what the str/ unicode type is an array of. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
