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 pitrou
Recipients alanmcintyre, pitrou, vstinner
Date 2011-01-21.15:12:22
SpamBayes Score 3.4958274e-09
Marked as misclassified No
Message-id <1295622740.3681.10.camel@localhost.localdomain>
In-reply-to <>
> > The question is, rather, why you need an external flag for that.
> Because I don't want to change the default encoding. I am not sure
> that all applications support UTF-8 encodings.

If this is a ZIP standard flag, why should we care about applications
which don't support it? Should we add other flags to disable other
features out of fear that other applications might not support them

> But if you control your environment, force UTF-8 encoding should
> improve your Unicode support.

How is a random user supposed to know if their tools support UTF-8
encoding? It's not like everyone is an expert in ZIP files. This is the
kind of situation where asking the user to make a choice is more
confusing than helpful. When adding the flag, not only you complicate
the API, but you have to support this flag for the rest of your life
(well, almost :-)).

We could instead use utf-8 by default for all non-ascii filenames (and
*perhaps* have a separate force_cp437 flag, but default it to False).
Date User Action Args
2011-01-21 15:12:25pitrousetrecipients: + pitrou, alanmcintyre, vstinner
2011-01-21 15:12:22pitroulinkissue10972 messages
2011-01-21 15:12:22pitroucreate