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 jgoerzen, jnalley, serhiy.storchaka
Date 2019-11-27.11:45:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574855152.56.0.654502565349.issue38861@roundup.psfhosted.org>
In-reply-to
Content
The standard requires interpreting filename encoding as cp470 or utf8. But for practical reasons it would be handy to allow to specify other encoding (which is not necessary equal ti the local filesystem encoding)
. This is issue28080. But i left this issue open so that we will not forget to ensure that it will be the option of using extractall() with the encoding that matches the encoding of the local zip tool. There may be percularities on Windows and macOS. Lso there should be an option for CLI.
History
Date User Action Args
2019-11-27 11:45:52serhiy.storchakasetrecipients: + serhiy.storchaka, jgoerzen, jnalley
2019-11-27 11:45:52serhiy.storchakasetmessageid: <1574855152.56.0.654502565349.issue38861@roundup.psfhosted.org>
2019-11-27 11:45:52serhiy.storchakalinkissue38861 messages
2019-11-27 11:45:52serhiy.storchakacreate