You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
decompressobj which is provided as an API-compatible interface with zlib.decompressobj does not support flush().
This makes it difficult to be used alongside zlib decompressor.
The text was updated successfully, but these errors were encountered:
In release 0.11.0, although flush() is now supported on decompressobj, it returns None unlike zlib.decompressobj which returns empty string.
From the python documentation:
Decompress.flush([length])
All pending input is processed, and a string containing the remaining uncompressed output is returned. After calling flush(), the decompress() method cannot be called again; the only realistic action is to delete the object.
The optional parameter length sets the initial size of the output buffer.
This behavior makes special handling needed for zstandard decompressor when using the return value directly in things like file object's write(), which do not accept None.
decompressobj
which is provided as an API-compatible interface withzlib.decompressobj
does not supportflush()
.This makes it difficult to be used alongside zlib decompressor.
The text was updated successfully, but these errors were encountered: