Adam Olsen <rhamph <at> gmail.com> writes: > > UTF-8b doesn't work as intended. It produces an invalid unicode > object (garbage surrogates) that cannot be used with external APIs or > libraries that require unicode.
At least it works with all Python operations supported by the unicode type (methods, concatenation, etc.) without any bad surprise. That feeding it to e.g. PyGTK may give bogus results is another problem. > If you don't need unicode then your > code should state so explicitly, and 8859-1 is ideal there. But then you can say bye-bye to proper representation (e.g. using print()) of even valid filenames. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
