Yudi Levi added the comment:
The main issue is that when extracting older zip files, files are actually
written to disk with corrupted (altered) names.
Unfortunately it's been a while since I saw this issue and I can't tell if it
was fixed or if I simply can't reproduce it
Change by Yudi :
--
keywords: +patch
pull_requests: +18698
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19333
___
Python tracker
<https://bugs.python.org/issu
Change by Yudi :
--
keywords: +patch
pull_requests: +18697
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19335
___
Python tracker
<https://bugs.python.org/issu
New submission from Yudi :
Some old zip files that don't yet use unicode file names might have entries
with characters beyond the ascii range.
ZipInfo seems to encode these file names with 'cp437' codepage (correct for old
zips) but decode them back with 'ascii' code
New submission from Yudi :
Updating the zip file comment to a shorter comment should truncate the zip file
at the end of the new comment.
Instead, the new comment is written to the zip file but the file length stays
the same.
For example, for a zip file that has the following zip comment
