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 lemburg
Recipients Jan Niklas Hasse, Sworddragon, abarry, akira, barry, ezio.melotti, lemburg, methane, ncoghlan, r.david.murray, vstinner, yan12125
Date 2017-01-05.11:36:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5aea9f92-d3a0-35c0-8081-13255c354620@egenix.com>
In-reply-to <1483613688.04.0.668880312544.issue28180@psf.upfronthosting.co.za>
Content
While going for the full locale setting may be a good option,
perhaps just focusing on the FS encoding for now is a better
way forward (and also more in line with the ticket title).

So essentially go for the PEP 529 approach on Unix as well
(except that we use 'ascii' as fallback in legacy mode):

https://www.python.org/dev/peps/pep-0529/

The PEP also includes a section on affected modules, which we
could double check (even though the term "FS encoding" implies
that only file system relevant APIs are touched by such a change,
the encoding is used in several other places as well):

https://www.python.org/dev/peps/pep-0529/#id14

For Windows, a couple of modules such as pwd and nis are not
used, so those may need some extra attention.
History
Date User Action Args
2017-01-05 11:36:20lemburgsetrecipients: + lemburg, barry, ncoghlan, vstinner, ezio.melotti, r.david.murray, methane, akira, Sworddragon, yan12125, abarry, Jan Niklas Hasse
2017-01-05 11:36:20lemburglinkissue28180 messages
2017-01-05 11:36:19lemburgcreate