cpython/Lib/test/output/test_zlib

test_zlib
0xe5c1a120 0x43b6aa94
0xbd602f7 0xbd602f7
expecting Bad compression level
expecting Invalid initialization option
expecting Invalid initialization option
normal compression/decompression succeeded
compress/decompression obj succeeded
decompress with init options succeeded
decompressobj with init options succeeded
should be '': ''
max_length decompressobj succeeded
unconsumed_tail should be '': ''
Testing on 17K of random data
generated by regrtest.py -g 1997-08-15 13:00:02 -03:00			`test_zlib`
Use hex() when outputting the various checksums so the test output is the same on 32 and 64 bit machines. 1998-04-24 15:31:28 -03:00			`0xe5c1a120 0x43b6aa94`
			`0xbd602f7 0xbd602f7`
Now produces some reassuring output. 1997-09-04 20:42:01 -03:00			`expecting Bad compression level`
			`expecting Invalid initialization option`
			`expecting Invalid initialization option`
			`normal compression/decompression succeeded`
			`compress/decompression obj succeeded`
			`decompress with init options succeeded`
			`decompressobj with init options succeeded`
[ #403753 ] zlib decompress; uncontrollable memory usage Mostly by Toby Dickenson and Titus Brown. Add an optional argument to a decompression object's decompress() method. The argument specifies the maximum length of the return value. If the uncompressed data exceeds this length, the excess data is stored as the unconsumed_tail attribute. (Not to be confused with unused_data, which is a separate issue.) Difference from SF patch: Default value for unconsumed_tail is "" rather than None. It's simpler if the attribute is always a string. 2001-10-16 17:39:49 -03:00			`should be '': ''`
			`max_length decompressobj succeeded`
			`unconsumed_tail should be '': ''`
Add test case from bug #124981: zlib decompress of sync-flushed data fails 2001-02-20 22:17:01 -04:00			`Testing on 17K of random data`