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 Arfrever, loewis, vstinner
Date 2010-05-20.17:23:03
SpamBayes Score 0.000757834
Marked as misclassified No
Message-id <4BF56FF6.60302@v.loewis.de>
In-reply-to <1274357365.37.0.0731450159524.issue8775@psf.upfronthosting.co.za>
Content
> 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 on OSX, or we find some Apple documentation
that can be taken as a specification.

I think the C locale is very poorly supported on OSX, and we shouldn't
really use it for anything. What may be useful is the terminal encoding
(which may be different both from UTF-8 and the locale encoding),
however, it's not possible to find out what the terminal encoding is.
In addition, programs may be started "directly" (i.e. not from the
terminal), in which case the terminal encoding would be irrelevant.

For file name arguments at least, it's very clear that the command line
arguments also use the file system encoding.
History
Date User Action Args
2010-05-20 17:23:05loewissetrecipients: + loewis, vstinner, Arfrever
2010-05-20 17:23:04loewislinkissue8775 messages
2010-05-20 17:23:03loewiscreate