➜

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 serhiy.storchaka
Recipients dholth, docs@python, r.david.murray, serhiy.storchaka, terry.reedy
Date 2016-06-24.17:29:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466789351.97.0.808044726831.issue27344@psf.upfronthosting.co.za>
In-reply-to
Content 
This note looks outdated.

In 2.x 8-bit file names are written as is, implying cp437 or what your consumers expect. Unicode file names are encoded to ascii or utf-8 (with setting utf-8 flag). In 3.x only Unicode file names are accepted, and they always are encoded to ascii or utf-8. There is no way to write non-ascii non-utf-8 file names. cp437 is not used at all.

Maybe just remove this misleading note?
History
Date User Action Args
2016-06-24 17:29:12serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy, r.david.murray, dholth, docs@python
2016-06-24 17:29:11serhiy.storchakasetmessageid: <1466789351.97.0.808044726831.issue27344@psf.upfronthosting.co.za>
2016-06-24 17:29:11serhiy.storchakalinkissue27344 messages
2016-06-24 17:29:11serhiy.storchakacreate