Sept. 5, 2017
9:15 a.m.
On 5 September 2017 at 01:36, Nathaniel Smith <njs@pobox.com> wrote:
On Tue, Sep 5, 2017 at 1:00 AM, Thomas Kluyver <thomas@kluyver.me.uk> wrote:
- We already have workarounds for the commonest case of UTF-8 paths + C locale: ignore the locale and treat paths as UTF-8.
Only in 3.7, I think? Or do you mean, backends should be doing this manually on Python 2?
The frontend controls the locale that the backend runs in, so the frontend can set C.UTF-8 even if the frontend itself is launched in the C locale. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia