[issue4272] set timestamp in gzip stream

2009-01-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: The patches have been committed, thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue4272] set timestamp in gzip stream

2009-01-01 Thread Jacques Frechet
Changes by Jacques Frechet : Added file: http://bugs.python.org/file12529/gzip-mtime-revised-2.x.patch ___ Python tracker ___ ___ Python-bugs-l

[issue4272] set timestamp in gzip stream

2009-01-01 Thread Jacques Frechet
Jacques Frechet added the comment: I am uploading a new patch, identical to the previous patch except that it does not contain the ill-advised third test case (test_literal_output). The patch still applies cleanly and the tests still pass. Added file: http://bugs.python.org/file12528/gzip-mtim

[issue4272] set timestamp in gzip stream

2008-12-31 Thread Antoine Pitrou
Antoine Pitrou added the comment: test_literal_output looks really too strict to me. At most, you could check that the header and trailer are unchanged, but it would probably make it equivalent to test_metadata. Other than that, I think it's an useful addition. -- nosy: +pitrou priority

[issue4272] set timestamp in gzip stream

2008-11-06 Thread Jacques Frechet
Jacques Frechet <[EMAIL PROTECTED]> added the comment: I'm no expert either. The output certainly seems to be deterministic for a given version of zlib, and I'm not aware of any prior versions of zlib that produce different compressed output. However, my understanding is that there is more than

[issue4272] set timestamp in gzip stream

2008-11-06 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I considered using a datetime.datetime object instead. But it make more sense to use a time_t number, like os.stat() and time.time(). About the tests on the gzip format details: I am not an expert of the gzip format, but are we sure t

[issue4272] set timestamp in gzip stream

2008-11-06 Thread Jacques Frechet
Jacques Frechet <[EMAIL PROTECTED]> added the comment: This discussion of the problem and possible workarounds might also be of interest: http://stackoverflow.com/questions/264224/setting-the-gzip-timestamp-from-python ___ Python tracker <[EMAIL PROTECTED]>

[issue4272] set timestamp in gzip stream

2008-11-06 Thread Jacques Frechet
Changes by Jacques Frechet <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11955/gzip-mtime-2.x.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4272] set timestamp in gzip stream

2008-11-06 Thread Jacques Frechet
New submission from Jacques Frechet <[EMAIL PROTECTED]>: The gzip header defined in RFC 1952 includes a mandatory "MTIME" field, originally intended to contain the modification time of the original uncompressed file. It is often ignored when decompressing, though gunzip (for example) uses it to