On Tue, Oct 15, 2013 at 03:46:15PM +0200, "Martin v. Löwis" wrote:
> Am 15.10.13 14:49, schrieb Daniel Holth:
> > It is part of the ZIP specification. CP437 or UTF-8 are the two
> > official choices, but other encodings happen on Russian, Japanese
> > systems.
>
> Indeed. Formally, the other encod
Am 15.10.13 14:49, schrieb Daniel Holth:
> It is part of the ZIP specification. CP437 or UTF-8 are the two
> official choices, but other encodings happen on Russian, Japanese
> systems.
Indeed. Formally, the other encodings are not supported by the
ZIP specification, and are thus formally misuse o
Hi!
On Tue, Oct 15, 2013 at 12:22:29PM +0200, "\"Martin v. L?wis\""
wrote:
> Am 15.10.13 10:53, schrieb Daniel Holth:
> > FYI zipfile does do UTF-8
> > (http://hg.python.org/cpython/file/d7ebe03fa752/Lib/zipfile.py#l368).
> > Only the non-Unicode encodings might need some help. I like that the
>
On Tue, Oct 15, 2013 at 8:02 AM, Steven D'Aprano wrote:
> On Tue, Oct 15, 2013 at 10:20:03AM +0200, Victor Stinner wrote:
>> Both issues are related and should be fixed in the *same* commit.
>> Python should provide an option to encode explicitly filenames to
>> UTF-8. Or maybe better: encode to U
On Tue, Oct 15, 2013 at 10:20:03AM +0200, Victor Stinner wrote:
> Both issues are related and should be fixed in the *same* commit.
> Python should provide an option to encode explicitly filenames to
> UTF-8. Or maybe better: encode to UTF-8 by default, with an option to
> encode to cp437, and anot
Am 15.10.13 10:53, schrieb Daniel Holth:
> FYI zipfile does do UTF-8
> (http://hg.python.org/cpython/file/d7ebe03fa752/Lib/zipfile.py#l368).
> Only the non-Unicode encodings might need some help. I like that the
> patch is only concerned with decoding. Is it necessary to support
> writing non-UTF8
FYI zipfile does do UTF-8
(http://hg.python.org/cpython/file/d7ebe03fa752/Lib/zipfile.py#l368).
Only the non-Unicode encodings might need some help. I like that the
patch is only concerned with decoding. Is it necessary to support
writing non-UTF8 encodings?
On Tue, Oct 15, 2013 at 10:20 AM, Victo
Both issues are related and should be fixed in the *same* commit.
Python should provide an option to encode explicitly filenames to
UTF-8. Or maybe better: encode to UTF-8 by default, with an option to
encode to cp437, and another to encode to an arbitrary encoding.
Victor
2013/10/15 Alexander Be
On Mon, Oct 14, 2013 at 6:13 PM, Victor Stinner
wrote:
> I opened an issue proposing exactly the same change, but I didn't provide a
> patch.
I found this:
http://bugs.python.org/issue10614
but it has (seemingly incorrect) patch.
Also related:
http://bugs.python.org/issue10972
Victor - is an
I opened an issue proposing exactly the same change, but I didn't provide a
patch. Thanks for working on the issue.
(Sorry I don't know the issue number. Search for "zipfile encoding".)
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://ma
Hello,
On Tue, 15 Oct 2013 00:55:05 +0400
Sergey Dorofeev wrote:
> Hello,
>
> I'd like to submit patch to support zip archives created on systems that
> use non-US codepage (e.g. russian CP866).
> Codepage would be specified in additional parameter of ZipFile
> constructor, named "codepage".
Hello,
I'd like to submit patch to support zip archives created on systems that
use non-US codepage (e.g. russian CP866).
Codepage would be specified in additional parameter of ZipFile
constructor, named "codepage".
If it is not specified, old behavior is preserved (use CP437).
--- zipfile.py
12 matches
Mail list logo
