Patrik Dufresne added the comment:
This bug is very old, any development on the subject. This issue is hitting me
trying to port my project (rdiffweb) to python3. It received a lot of broken
filename with invalid encoding and I need to create a meaningful Zip archive
with it. Currently, it
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: -ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10757
___
___
Python-bugs-list
Changes by Ernest ozial...@gmail.com:
--
nosy: +ozialien
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10757
___
___
Python-bugs-list mailing list
Changes by Ethan Furman et...@stoneleaf.us:
--
nosy: +ethan.furman
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10757
___
___
Python-bugs-list
R. David Murray rdmur...@bitdance.com added the comment:
Well, this is the same
treat-strings-and-byte-strings-equivalently-in-the-same-API problem that we've
had elsewhere. It'll require a bit of refactoring to make it work.
On read zipfile decodes filenames using cp437 if the utf-8 flag
