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 vstinner
Recipients benjamin.peterson, gz, r.david.murray, vstinner
Date 2011-12-20.19:37:40
SpamBayes Score 6.180731e-09
Marked as misclassified No
Message-id <1324409861.03.0.901067638959.issue13643@psf.upfronthosting.co.za>
In-reply-to
Content
> Currently when running Python on a non-OSX posix environment
> under either the C locale, or with an invalid or missing locale,
> it's not possible to operate using unicode filenames outside
> the ascii range.

It was already discussed: using a different encoding for filenames and for other things is really not a good idea. The main problem is the interaction with other programs.

Read discussion of issues #8622, #8775 and #9992.
History
Date User Action Args
2011-12-20 19:37:41vstinnersetrecipients: + vstinner, benjamin.peterson, r.david.murray, gz
2011-12-20 19:37:41vstinnersetmessageid: <1324409861.03.0.901067638959.issue13643@psf.upfronthosting.co.za>
2011-12-20 19:37:40vstinnerlinkissue13643 messages
2011-12-20 19:37:40vstinnercreate