Martin v. Löwis <mar...@v.loewis.de> added the comment: > 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). ---------- title: Command line arguments are not correctly decodediflocale and fileystem encodingsaredifferent -> Command line arguments are not correctly decodediflocale and fileystem encodingsaredifferent _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9992> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
