This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients doko, kraai, r.david.murray, terry.reedy
Date 2010-09-07.10:12:51
SpamBayes Score 7.1362973e-07
Marked as misclassified No
Message-id <1283854373.85.0.153071483458.issue9664@psf.upfronthosting.co.za>
In-reply-to
Content
Matt: if you want to learn the file format and propose a patch, I think it would be OK for gzip to duck-type the file object and only raise an error when a seek is explicitly requested.  After all, that's the way real file objects work.  A quick glance at the code, though, indicates this isn't a trivial refactoring.  I think it should be possible in theory since one can pipe a gzipped file into gunzip, and I don't think it buffers the whole file to unzip it...but I don't know for sure. Another issue is that if the patch substantially changes the memory/performance footprint it might get rejected on that basis.

If you (or anyone else) wants to work on a patch let me know and I'll reopen the issue.
History
Date User Action Args
2010-09-07 10:12:54r.david.murraysetrecipients: + r.david.murray, terry.reedy, doko, kraai
2010-09-07 10:12:53r.david.murraysetmessageid: <1283854373.85.0.153071483458.issue9664@psf.upfronthosting.co.za>
2010-09-07 10:12:52r.david.murraylinkissue9664 messages
2010-09-07 10:12:51r.david.murraycreate