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 r.david.murray
Recipients benjamin.peterson, gz, pitrou, poolie, r.david.murray, vila, vstinner
Date 2011-12-22.04:05:35
SpamBayes Score 9.690636e-07
Marked as misclassified No
Message-id <1324526735.87.0.33078398812.issue13643@psf.upfronthosting.co.za>
In-reply-to
Content
> _My_ locale is set properly.  The problem is all the other
> people in the world who do not have their locale set to match
> their files on disk; telling them each to fix it is tedious.
> But perhaps the OS is the best place to address that, when the
> incorrect locale is just accidental not unavoidable.

I fixed my locale back before my OS fully supported doing so.
It was painful, but it was *so* worth it.  There were many
tools that just worked better after I did that, and several
tools that I had to convince to use utf-8 through non-standard
means.

So I think Python is doing the right thing by using the locale
(the Standard Way), and that getting the OS vendors and/or
the users to fix their locale settings is indeed the right place
to fix this.
History
Date User Action Args
2011-12-22 04:05:35r.david.murraysetrecipients: + r.david.murray, pitrou, vstinner, vila, benjamin.peterson, gz, poolie
2011-12-22 04:05:35r.david.murraysetmessageid: <1324526735.87.0.33078398812.issue13643@psf.upfronthosting.co.za>
2011-12-22 04:05:35r.david.murraylinkissue13643 messages
2011-12-22 04:05:35r.david.murraycreate