On Tue, Jun 22, 2010 at 4:49 PM, Stephen J. Turnbull <step...@xemacs.org> wrote: > > Which works if and only if your outputs are truly unicode-able. > > With PEP 383, they always are, as long as you allow Unicode to be > decoded to the same garbage your bytes-based program would have > produced anyway.
Could it be that part of the problem here is that we need to better advertise "errors='surrogateescape'" as a mechanism for decoding incorrectly encoded data according to a nominal codec without throwing UnicodeDecode and UnicodeEncode errors all over the place? Currently it only garners a mention in the docs in the context of the os module, the list of error handlers in the codecs module and as a default error handler argument in the tarfile module. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
