Martin v. Löwis <mar...@v.loewis.de> added the comment: Am 09.10.2010 14:07, schrieb Antoine Pitrou: > > Antoine Pitrou <pit...@free.fr> added the comment: > >> For the command line, it would mean that we >> introduced a new encoding: "command line encoding", which will be utf-8 on >> OSX. > > Or more generally "environment encoding", if it's also used for env > vars. This could solve the subprocess issue neatly.
Please no. We run into problems because we have two inconsistent encodings, and now you propose to introduce another one, allowing for even more inconsistencies??? ---------- 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
