➜

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 loewis
Recipients ixokai, lemburg, loewis, pitrou, pjenvey, ronaldoussoren, vstinner
Date 2010-10-11.14:38:38
SpamBayes Score 0.000539122
Marked as misclassified No
Message-id <4CB3216D.4020804@v.loewis.de>
In-reply-to <70b6a53c-7aee-c2c0-b567-b3fd31ca1052@me.com>
Content 
> There is one reason for not wanting to assume that the encoding is
> always UTF-8: the user might access the system from a non-UTF8
> terminal (such as when logging in with an SSH session from a system
> not using UTF-8, or using an alternate terminal application). IMHO
> these are minor enough use-cases that we could just enforce that the
> encoding is UTF-8 on OSX.

Ok, that's enough of an expert statement for me to settle the OSX
case: we will always assume that environment data is UTF-8 on OSX
(leaving the rest to the surrogate escape handler).
History
Date User Action Args
2010-10-11 14:38:40loewissetrecipients: + loewis, lemburg, ixokai, ronaldoussoren, pitrou, vstinner, pjenvey
2010-10-11 14:38:38loewislinkissue9992 messages
2010-10-11 14:38:38loewiscreate