Author poolie
Recipients benjamin.peterson, gz, poolie, r.david.murray, vstinner
Date 2011-12-20.23:53:28
SpamBayes Score 0.00163966
Marked as misclassified No
Message-id <1324425209.38.0.934256426551.issue13643@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm not sure why having a locale set to C or something invalid should be considered a Python bug. 

Programs like bzr that hit these problems can tell their users, either in the docs or an error message, "change your locale to a UTF-8 one".

There are two problems with this: one is just the practical one that it scales poorly to have to tell every user to do this and to take them through working out how to set this in a way that covers cron jobs, daemons, things run over ssh, etc.

The other problem is that the locale variables primarily describe the locale for input/output, and that can very reasonably be different from the filesystem encoding.  As a specific common example people may have UTF-8 filenames but want a C locale terminal.  If there was a separate LC_FILENAMES then Python could respect that and insist people set it, but there isn't.
History
Date User Action Args
2011-12-20 23:53:29pooliesetrecipients: + poolie, vstinner, benjamin.peterson, r.david.murray, gz
2011-12-20 23:53:29pooliesetmessageid: <1324425209.38.0.934256426551.issue13643@psf.upfronthosting.co.za>
2011-12-20 23:53:28poolielinkissue13643 messages
2011-12-20 23:53:28pooliecreate