summaryrefslogtreecommitdiffstats
path: root/Demo/scripts
diff options
context:
space:
mode:
authorAndrew M. Kuchling <amk@amk.ca>2003-02-05 21:35:07 (GMT)
committerAndrew M. Kuchling <amk@amk.ca>2003-02-05 21:35:07 (GMT)
commit64edd6ac1ddb29f7817ee44e9b376b096ffa1d55 (patch)
tree1dac9b2c32aed3e7beed2cb29aef687acd355504 /Demo/scripts
parent570e35870a131dc65dde2835972abb6fdf60a117 (diff)
downloadcpython-64edd6ac1ddb29f7817ee44e9b376b096ffa1d55.zip
cpython-64edd6ac1ddb29f7817ee44e9b376b096ffa1d55.tar.gz
cpython-64edd6ac1ddb29f7817ee44e9b376b096ffa1d55.tar.bz2
[Patch #654421 from Matthew Mueller]
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.
Diffstat (limited to 'Demo/scripts')
0 files changed, 0 insertions, 0 deletions