On Tue, May 23, 2017, at 09:08 AM, Paul Moore wrote: > I strongly > prefer using the locale encoding as the assumed encoding for the > output stream rather than UTF-8.
I may have missed it, but has anyone proposed what it should do if it wants to send characters which can't be encoded in the locale encoding? Paths on Windows are handled natively as UTF-16, as I understand it, so it's entirely possible for them to contain characters which can't be represented in, say, CP1252. Given this, and the workarounds Nick has pointed out are necessary for systems where the locale thinks it's ASCII, I still think that specifying "UTF-8" is a better option than trying to work with locale encodings. We're building a new spec for new tools in 2017, let's not prolong the pain of platform-dependent default encodings further. Thomas _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
