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 gz
Recipients benjamin.peterson, gz, r.david.murray, vstinner
Date 2011-12-20.20:24:43
SpamBayes Score 9.970791e-10
Marked as misclassified No
Message-id <1324412684.22.0.763687005894.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.  You have to handle un-decodable filenames no
> matter what you do, since things aren't always encoded in utf-8 on non-OSX
> unix even when that is the system locale.  It's just something you have to
> live with.

This is more about un-encodable filenames. At the moment work with non-ascii filenames in Python robustly requires two branches, one using unicode and one that encodes to bytestrings and deals with the case where the name can't be represented in the declared filesystem encoding. That may be something that just had to be lived with, but it's a little annoying when even without a UTF-8 locale for a particular process, that's what most systems will want on disk.
History
Date User Action Args
2011-12-20 20:24:44gzsetrecipients: + gz, vstinner, benjamin.peterson, r.david.murray
2011-12-20 20:24:44gzsetmessageid: <1324412684.22.0.763687005894.issue13643@psf.upfronthosting.co.za>
2011-12-20 20:24:43gzlinkissue13643 messages
2011-12-20 20:24:43gzcreate