Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Issue #23865: close() methods in multiple modules now are idempotent and more | Serhiy Storchaka | 2015-04-10 | 1 | -12/+14 |
| | | | | | robust at shutdown. If needs to release multiple resources, they are released even if errors are occured. | ||||
* | Issue #21560: An attempt to write a data of wrong type no longer cause | Serhiy Storchaka | 2015-03-23 | 1 | -2/+2 |
| | | | | GzipFile corruption. Original patch by Wolfgang Maier. | ||||
* | Issue #13664: GzipFile now supports non-ascii Unicode filenames. | Serhiy Storchaka | 2014-10-12 | 1 | -3/+10 |
| | |||||
* | backout 214d8909513d for regressions (#1159051) | Benjamin Peterson | 2013-05-11 | 1 | -33/+36 |
| | |||||
* | Close #17666: Fix reading gzip files with an extra field. | Serhiy Storchaka | 2013-04-08 | 1 | -1/+2 |
| | |||||
* | Issue #1159051: GzipFile now raises EOFError when reading a corrupted file | Serhiy Storchaka | 2013-01-22 | 1 | -36/+32 |
| | | | | | with truncated header or footer. Added tests for reading truncated gzip and bzip2 files. | ||||
* | Issue #15677: Document that zlib and gzip accept a compression level of 0 to ↵ | Nadeem Vawda | 2012-11-11 | 1 | -2/+3 |
| | | | | | | mean 'no compression'. Patch by Brian Brazil. | ||||
* | Bug #16441: avoid excessive memory usage working with large gzip files | Chris Withers | 2012-11-09 | 1 | -2/+2 |
| | |||||
* | Issue #5148: Ignore 'U' in mode given to gzip.open() and gzip.GzipFile(). | Nadeem Vawda | 2012-10-21 | 1 | -0/+4 |
| | |||||
* | Issue #13781: Fix GzipFile to work with os.fdopen()'d file objects. | Nadeem Vawda | 2012-01-18 | 1 | -2/+6 |
| | |||||
* | Merged revisions 85291 via svnmerge from | Antoine Pitrou | 2010-10-06 | 1 | -0/+10 |
| | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r85291 | antoine.pitrou | 2010-10-06 23:21:18 +0200 (mer., 06 oct. 2010) | 4 lines Issue #9759: GzipFile now raises ValueError when an operation is attempted after the file is closed. Patch by Jeffrey Finkelstein. ........ | ||||
* | Fix test_gzip failure on OS X. The failure was a result of trying to fflush | Mark Dickinson | 2010-05-04 | 1 | -1/+1 |
| | | | | a file that wasn't open for writing. Patch by Antoine Pitrou. | ||||
* | Issue #2846: Add support for gzip.GzipFile reading zero-padded files. | Antoine Pitrou | 2010-01-13 | 1 | -0/+9 |
| | | | | Patch by Brian Curtin. | ||||
* | Issue #7471: Improve the performance of GzipFile's buffering mechanism, | Antoine Pitrou | 2010-01-03 | 1 | -57/+42 |
| | | | | | and make it implement the `io.BufferedIOBase` ABC to allow for further speedups by wrapping it in an `io.BufferedReader`. Patch by Nir Aides. | ||||
* | Issue #4750: Store the basename of the original filename in | Lars Gustäbel | 2009-10-29 | 1 | -2/+2 |
| | | | | the gzip FNAME header as required by RFC 1952. | ||||
* | #4351: more appropriate DeprecationWarning stacklevels | Philip Jenvey | 2009-05-08 | 1 | -1/+1 |
| | |||||
* | Issue #3860: GzipFile and BZ2File now support the context manager protocol. | Antoine Pitrou | 2009-01-10 | 1 | -0/+8 |
| | |||||
* | Issue #4272: Add an optional argument to the GzipFile constructor to ↵ | Antoine Pitrou | 2009-01-04 | 1 | -4/+17 |
| | | | | override the timestamp in the gzip stream. | ||||
* | #2959: allow multiple close() calls for GzipFile. | Georg Brandl | 2008-05-25 | 1 | -0/+2 |
| | |||||
* | prevent a warning from the struct module when data size >= 2**32. | Gregory P. Smith | 2008-03-23 | 1 | -1/+1 |
| | |||||
* | A bugfix for r61813, it would fail if the data size was >=2**32. | Gregory P. Smith | 2008-03-23 | 1 | -5/+1 |
| | |||||
* | Fix gzip to deal with CRC's being signed values in Python 2.x properly and to | Gregory P. Smith | 2008-03-23 | 1 | -31/+13 |
| | | | | | | | read 32bit values as unsigned to start with rather than applying signedness fixups allover the place afterwards. This hopefully fixes the test_tarfile failure on the alpha/tru64 buildbot. | ||||
* | Improve the error message when the CRCs don't match. | Gregory P. Smith | 2008-03-19 | 1 | -1/+2 |
| | |||||
* | Strip the '.gz' extension from the filename that is written to the | Lars Gustäbel | 2007-02-13 | 1 | -3/+6 |
| | | | | gzip header. | ||||
* | Patch #1647484: Renamed GzipFile's filename attribute to name. The | Lars Gustäbel | 2007-02-13 | 1 | -8/+13 |
| | | | | | filename attribute is still accessible as a property that emits a DeprecationWarning. | ||||
* | Patch #1355023: support whence argument for GzipFile.seek. | Martin v. Löwis | 2006-11-12 | 1 | -1/+6 |
| | |||||
* | Try to squash struct.pack warnings on the "amd64 gentoo trunk" | Tim Peters | 2006-08-02 | 1 | -1/+7 |
| | | | | | | | | | | | | | | | | | | | | buildbot (& possibly other 64-bit boxes) during test_gzip. The native zlib crc32 function returns an unsigned 32-bit integer, which the Python wrapper implicitly casts to C long. Therefore the same crc can "look negative" on a 32-bit box but "look positive" on a 64-bit box. This patch papers over that platform difference when writing the crc to file. It may be better to change the Python wrapper, either to make the result "look positive" on all platforms (which means it may have to return a Python long at times on a 32-bit box), or to keep the sign the same across boxes. But that would be a visible change in what users see, while the current hack changes no visible behavior (well, apart from stopping the struct deprecation warning). Note that the module-level write32() function is no longer used. | ||||
* | Apply revised patch for GzipFile.readline performance #1281707 | Bob Ippolito | 2006-05-22 | 1 | -16/+21 |
| | |||||
* | Revert gzip readline performance patch #1281707 until a more generic ↵ | Bob Ippolito | 2006-05-22 | 1 | -28/+20 |
| | | | | performance improvement can be found | ||||
* | GzipFile.readline performance improvement (~30-40%), patch #1281707 | Bob Ippolito | 2006-05-22 | 1 | -20/+28 |
| | |||||
* | [Bug #1074261, patch #1074381] Restrict the size of chunks read from the ↵ | Andrew M. Kuchling | 2005-06-09 | 1 | -2/+3 |
| | | | | file in order to avoid overflow or huge memory consumption. Patch by Mark Eichin | ||||
* | Whitespace normalization. | Tim Peters | 2005-03-28 | 1 | -2/+2 |
| | |||||
* | Patch #1110248: SYNC_FLUSH the zlib buffer for GZipFile.flush. | Martin v. Löwis | 2005-03-03 | 1 | -1/+4 |
| | | | | Partially fixes #1110242. | ||||
* | Ack, removed useless import of os I just introduced. | Tim Peters | 2004-07-27 | 1 | -1/+1 |
| | |||||
* | Added a new fileno() method. ZODB's repozo.py wants this so it can | Tim Peters | 2004-07-27 | 1 | -1/+9 |
| | | | | apply os.fsync() to the GzipFile backup files it creates. | ||||
* | Replace backticks with repr() or "%r" | Walter Dörwald | 2004-02-12 | 1 | -1/+1 |
| | | | | From SF patch #852334. | ||||
* | Fix error in exception message. | Brett Cannon | 2003-12-04 | 1 | -1/+1 |
| | |||||
* | [Patch #654421 from Matthew Mueller] | Andrew M. Kuchling | 2003-02-05 | 1 | -2/+2 |
| | | | | | | | | | gzip shouldn't raise ValueError on corrupt files Currently the gzip module will raise a ValueError if the file was corrupt (bad crc or bad size). I can't see how that applies to reading a corrupt file. IOError seems better, and it's what code will likely be looking for. | ||||
* | Another round on SF patch 618135: gzip.py and files > 2G | Tim Peters | 2002-11-05 | 1 | -4/+9 |
| | | | | | | | | | | The last round boosted "the limit" from 2GB to 4GB. This round gets rid of the 4GB limit. For files > 4GB, gzip stores just the last 32 bits of the file size, and now we play along with that too. Tested by hand (on a 6+GB file) on Win2K. Boosting from 2GB to 4GB was arguably enough "a bugfix". Going beyond that smells more like "new feature" to me. | ||||
* | Related to SF patch 618135: gzip.py and files > 2G. | Tim Peters | 2002-11-04 | 1 | -18/+34 |
| | | | | | | | | | | | | | | | | Fixed the signed/unsigned confusions when dealing with files >= 2GB. 4GB is still a hard limitation of the gzip file format, though. Testing this was a bitch on Win98SE due to frequent system freezes. It didn't freeze while running gzip, it kept freezing while trying to *create* a > 2GB test file! This wasn't Python's doing. I don't know of a reasonable way to test this functionality in regrtest.py, so I'm not checking in a test case (a test case would necessarily require creating a 2GB+ file first, using gzip to zip it, using gzip to unzip it again, and then compare before-and-after; so >4GB free space would be required, and a loooong time; I did all this "by hand" once). Bugfix candidate, I guess. | ||||
* | Remove mention of deprecated xreadlines method. | Guido van Rossum | 2002-08-06 | 1 | -1/+1 |
| | |||||
* | Patch 560023 adding docstrings. 2.2 Candidate (after verifying modules were ↵ | Raymond Hettinger | 2002-05-29 | 1 | -0/+38 |
| | | | | not updated after 2.2). | ||||
* | force gzip module to open files using 'b'inary mode. | Skip Montanaro | 2002-05-23 | 1 | -0/+4 |
| | | | | closes patch #536278. | ||||
* | Whitespace normalization. | Tim Peters | 2002-04-16 | 1 | -2/+2 |
| | |||||
* | Partial introduction of bools where appropriate. | Guido van Rossum | 2002-04-07 | 1 | -11/+11 |
| | |||||
* | Make GzipFile an iterator. Closes bug #532621. | Neil Schemenauer | 2002-03-20 | 1 | -0/+10 |
| | |||||
* | Patch #443899: Check modes on files before performing operations. | Martin v. Löwis | 2002-03-11 | 1 | -1/+9 |
| | | | | Use IOErrors where file objects use them. | ||||
* | "f" should be "self"; reported by Neal Norwitz. | Fred Drake | 2001-10-13 | 1 | -1/+1 |
| | |||||
* | Remove redefinition of writelines() method | Andrew M. Kuchling | 2001-08-13 | 1 | -5/+0 |
| | | | | Remove unused variable and import | ||||
* | Whitespace normalization. | Tim Peters | 2001-08-09 | 1 | -2/+2 |
| |