[Python-Dev] Lack of sequential decompression in the zipfile module (original) (raw)

Alan McIntyre alan.mcintyre at gmail.com
Sat Feb 17 20:48:38 CET 2007

On 2/16/07, Derek Shockey <derek.shockey at gmail.com> wrote:

Since I was writing a script to work with potentially very large zipped files, I took it upon myself to write an extract() method for zipfile, which is essentially an adaption of the read() method modeled after tarfile's extract(). I feel that this is something that should really be provided in the zipfile module to make it more usable. I'm wondering if this has been discussed before, or if anyone has ever viewed this as a problem. I can post the code I wrote as a patch, though I'm not sure if my file IO handling is as robust as it needs to be for the stdlib. I'd appreciate any insight into the issue or direction on where I might proceed from here so as to fix what I see as a significant problem.

I ran into the same thing and made a patch a long while ago (the one Martin mentioned):

https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1121142&group_id=5470

I am actually working on it this weekend; if you'd like to exchange code/test cases/whatever feel free to send me your stuff. I'll try to get a patch that works against the trunk posted today or tomorrow if you want to try it out.

Cheers, Alan

More information about the Python-Dev mailing list