[issue8775] Use locale encoding to decode sys.argv, not the file system encoding

2010-06-18 Thread STINNER Victor
STINNER Victor added the comment: Attached patch is a draft adding a new encoding: command line encoding. It is used to encode (subprocess) and decode (python) the command line arguments. It adds sys.getcmdlineencoding(). -- keywords: +patch Added file: http://bugs.python.org/file1771

[issue8775] Use locale encoding to decode sys.argv, not the file system encoding

2010-05-26 Thread STINNER Victor
STINNER Victor added the comment: @loewis: You restored the original (wrong) title "Use locale encoding to decode sys.argv, not the file system encoding", instead of the new (good) title "Use locale encoding to encode command line arguments (subprocess, os.exec*(), etc.)". Is it wanted or not

[issue8775] Use locale encoding to decode sys.argv, not the file system encoding

2010-05-20 Thread Martin v . Löwis
Martin v. Löwis added the comment: > I think that we should use the locale encoding to encode and decode command > line arguments. I disagree. IIUC, this is only about OSX. Now, we shouldn't take any action until either some OSX expert explains us how command line arguments are being passed o

[issue8775] Use locale encoding to decode sys.argv, not the file system encoding

2010-05-20 Thread STINNER Victor
New submission from STINNER Victor : The file system is hardcoded to UTF-8 on Mac OS X, whereas the locale encoding... depends on the locale. See issue #4388 for the details. I think that we should use the locale encoding to encode and decode command line arguments. We have to create a new enc