You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add support for bzip2 compression to the zipfile module #58579
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2012-05-01.05:59:21.119>created_at=<Date2012-03-20.11:30:40.849>labels= ['type-feature', 'library']
title='Add support for bzip2 compression to the zipfile module'updated_at=<Date2012-05-01.05:59:21.118>user='https://github.com/serhiy-storchaka'
ZIP File Format Specification (http://www.pkware.com/documents/casestudies/APPNOTE.TXT) supports bzip2 compression since at least 2003. Since bzip2 contained in Python standart library, it would be nice to add support for these method in zipfile. This will allow to process more foreign zip files and create more compact distributives.
The proposed patch adds new method ZIP_BZIP2, which is automatically detecting when unpacking and that can be used for packing.
I am working on this. Should I add tests to test_zipfile.py or create new test_zipfile_bzip2.py?
It would add a note that the bzip2 compression can understand not all programs (and do not understand the older versions of Python), but understands the Info-Unzip? My English is not enough for the documentation.
loewis commented on Mar 20, 2012
loewismannequin
Mannequin
More actions
Please add it to test_zipfile.
As for the documentation, I propose the wording
"bzip2 compression was added to the zip file format in 2001. However, even more recent tools (including older Python releases) may not support it, causing either refusal to process the zip file altogether, or faiilure to extract individual files."
I'm not a native speaker of English, either. Feel free to put things through Google translate; some native speaker will pick up the text and correct it.
Thanks to the tests, I found the error. Since the bzip2 is block algorithm, decompressor need to eat a certain amount of data, so it began to return data. Now when reading small chunks turns out premature end of data. I'm working on a fix.
All errors are fixed. All tests are passed. Unfortunately, the patch was more than expected. This is necessary for correct and effective work with large bzip2 buffers (for other codecs can also be a profit).
nadeemvawda commented on Mar 23, 2012
nadeemvawdamannequin
Mannequin
More actions
[Adding Alan McIntyre, who is listed as zipfile's maintainer.]
I haven't yet had a chance to properly familiarize myself with the
zipfile module, but I did notice an issue in the changes to ZipExtFile's
read() method. The existing code uses the b"".join() idiom for linear-
time concatenation, but the patch replaces it with a version that does
"buf += data" after each read. CPython can (I think) do this efficiently,
but it can be much slower on other implementations.
Martin:
As for the documentation, I propose the wording
"bzip2 compression was added to the zip file format in 2001. However, even more recent tools (including older Python releases) may not support it, causing either refusal to process the zip file altogether, or faiilure to extract individual files."
How about this?
"The zip format specification has included support for bzip2 compression
since 2001. However, some tools (including older Python releases) do not
support it, and may either refuse to process the zip file altogether, or
fail to extract individual files."
The existing code uses the b"".join() idiom for linear-
time concatenation, but the patch replaces it with a version that does
"buf += data" after each read.
You made a mess. The existing code uses buf += data, but I allowed myself
to replace it with the b"".join() idiom. The bzip2 codec has to deal with
large pieces of data, now this may be important. In read1 still used buf += data, but not in loop, there is a concatenation of the only two pieces.
"The zip format specification has included support for bzip2 compression
Thank you. Can you offer the variant with including both bzip2 and lzma
(supported since 2006)? I put him in the upcoming patch that adds support for
lzma compression to the zipfile module.
nadeemvawda commented on Mar 23, 2012
nadeemvawdamannequin
Mannequin
More actions
You made a mess. The existing code uses buf += data, but I allowed myself
to replace it with the b"".join() idiom. The bzip2 codec has to deal with
large pieces of data, now this may be important. In read1 still used buf += data, but not in loop, there is a concatenation of the only two pieces.
My mistake; I confused the bodies of read() and read1().
Thank you. Can you offer the variant with including both bzip2 and lzma
(supported since 2006)? I put him in the upcoming patch that adds support for
lzma compression to the zipfile module.
"The zip format specification has included support for bzip2 compression
since 2001, and for LZMA compression since 2006. However, some tools
(including older Python releases) do not support these compression
methods, and may either refuse to process the zip file altogether,
or fail to extract individual files."
buf += data is noticeably faster b''.join() in CPython.
Perhaps because your system's memory allocator is extremely good (or buf is always very small), but b''.join() is far more robust.
Another alternative is accumulating in a bytearray, since it uses overallocation for linear time appending.
Perhaps because your system's memory allocator is extremely good (or buf is always very small), but b''.join() is far more robust.
Another alternative is accumulating in a bytearray, since it uses overallocation for linear time appending.
I thought, that it was in special optimization, mentioned in the
python-dev, but could not find this in the code. Perhaps it had not been
implemented.
In this particular case, the bytes appending is performed only once (and
probably a lot of appending with b''). Exceptions are possible only in
pathological cases, for example when compressed data is much larger
uncompressed data. The current implementation uses buf += data, if
someone wants to change it, then it's not me.
Activity
serhiy-storchaka commentedon Mar 20, 2012
ZIP File Format Specification (http://www.pkware.com/documents/casestudies/APPNOTE.TXT) supports bzip2 compression since at least 2003. Since bzip2 contained in Python standart library, it would be nice to add support for these method in zipfile. This will allow to process more foreign zip files and create more compact distributives.
The proposed patch adds new method ZIP_BZIP2, which is automatically detecting when unpacking and that can be used for packing.
loewis commentedon Mar 20, 2012
Can you please submit a contributor form?
http://python.org/psf/contrib/contrib-form/
http://python.org/psf/contrib/
loewis commentedon Mar 20, 2012
The patch looks good. Can you also provide a test case?
serhiy-storchaka commentedon Mar 20, 2012
I am working on this. Should I add tests to test_zipfile.py or create new test_zipfile_bzip2.py?
It would add a note that the bzip2 compression can understand not all programs (and do not understand the older versions of Python), but understands the Info-Unzip? My English is not enough for the documentation.
loewis commentedon Mar 20, 2012
Please add it to test_zipfile.
As for the documentation, I propose the wording
"bzip2 compression was added to the zip file format in 2001. However, even more recent tools (including older Python releases) may not support it, causing either refusal to process the zip file altogether, or faiilure to extract individual files."
I'm not a native speaker of English, either. Feel free to put things through Google translate; some native speaker will pick up the text and correct it.
serhiy-storchaka commentedon Mar 21, 2012
Thanks to the tests, I found the error. Since the bzip2 is block algorithm, decompressor need to eat a certain amount of data, so it began to return data. Now when reading small chunks turns out premature end of data. I'm working on a fix.
serhiy-storchaka commentedon Mar 22, 2012
All errors are fixed. All tests are passed. Unfortunately, the patch was more than expected. This is necessary for correct and effective work with large bzip2 buffers (for other codecs can also be a profit).
nadeemvawda commentedon Mar 23, 2012
[Adding Alan McIntyre, who is listed as zipfile's maintainer.]
I haven't yet had a chance to properly familiarize myself with the
zipfile module, but I did notice an issue in the changes to ZipExtFile's
read() method. The existing code uses the b"".join() idiom for linear-
time concatenation, but the patch replaces it with a version that does
"buf += data" after each read. CPython can (I think) do this efficiently,
but it can be much slower on other implementations.
Martin:
How about this?
"The zip format specification has included support for bzip2 compression
since 2001. However, some tools (including older Python releases) do not
support it, and may either refuse to process the zip file altogether, or
fail to extract individual files."
serhiy-storchaka commentedon Mar 23, 2012
You made a mess. The existing code uses
buf += data, but I allowed myselfto replace it with the
b"".join()idiom. The bzip2 codec has to deal withlarge pieces of data, now this may be important. In read1 still used
buf += data, but not in loop, there is a concatenation of the only two pieces.Thank you. Can you offer the variant with including both bzip2 and lzma
(supported since 2006)? I put him in the upcoming patch that adds support for
lzma compression to the zipfile module.
nadeemvawda commentedon Mar 23, 2012
My mistake; I confused the bodies of read() and read1().
"The zip format specification has included support for bzip2 compression
since 2001, and for LZMA compression since 2006. However, some tools
(including older Python releases) do not support these compression
methods, and may either refuse to process the zip file altogether,
or fail to extract individual files."
serhiy-storchaka commentedon Mar 23, 2012
Fixed regeression in decompression.
Nadeem Vawda, we both were wrong.
buf += datais noticeably fasterb''.join()in CPython.loewis commentedon Apr 17, 2012
What's the status of your contrib form?
pitrou commentedon Apr 18, 2012
Perhaps because your system's memory allocator is extremely good (or buf is always very small), but b''.join() is far more robust.
Another alternative is accumulating in a bytearray, since it uses overallocation for linear time appending.
serhiy-storchaka commentedon Apr 19, 2012
Oops. I put this off for a detailed study and forgotten.
I will send the form, as only get to the printer and the scanner.
serhiy-storchaka commentedon Apr 19, 2012
I thought, that it was in special optimization, mentioned in the
python-dev, but could not find this in the code. Perhaps it had not been
implemented.
In this particular case, the bytes appending is performed only once (and
probably a lot of appending with b''). Exceptions are possible only in
pathological cases, for example when compressed data is much larger
uncompressed data. The current implementation uses
buf += data, ifsomeone wants to change it, then it's not me.
python-dev commentedon May 1, 2012
New changeset 028e8e0b03e8 by Martin v. Löwis in branch 'default':
Issue bpo-14371: Support bzip2 in zipfile module.
http://hg.python.org/cpython/rev/028e8e0b03e8
loewis commentedon May 1, 2012
Thanks for the patch!