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 pitrou
Recipients benjamin.peterson, gz, pitrou, poolie, r.david.murray, vstinner
Date 2011-12-21.01:16:19
SpamBayes Score 1.6822629e-06
Marked as misclassified No
Message-id <1324430181.75.0.96576790642.issue13643@psf.upfronthosting.co.za>
In-reply-to
Content
So, you're complaining about something which works, kind of:

$ touch héhé
$ LANG=C python3 -c "import os; print(os.listdir())"
['h\udcc3\udca9h\udcc3\udca9']

> This makes robustly working with non-ascii filenames on different
> platforms needlessly annoying, given no modern nix should have problems
> just using UTF-8 in these cases.

So why don't these supposedly "modern" systems at least set the appropriate environment variables for Python to infer the proper character encoding?
(since these "modern" systems don't have a well-defined encoding...)

Answer: because they are not modern at all, they are antiquated, inadapted and obsolete pieces of software designed and written by clueless Anglo-American people. Please report bugs against these systems. The culprit is not Python, it's the Unix crap and the utterly clueless attitude of its maintainers ("filesystems are just bytes", yeah, whatever...).
History
Date User Action Args
2011-12-21 01:16:23pitrousetrecipients: + pitrou, vstinner, benjamin.peterson, r.david.murray, gz, poolie
2011-12-21 01:16:21pitrousetmessageid: <1324430181.75.0.96576790642.issue13643@psf.upfronthosting.co.za>
2011-12-21 01:16:21pitroulinkissue13643 messages
2011-12-21 01:16:19pitroucreate