Now
MAIN commitmail json YAML
pkgsrc/archivers/py-zstandard/Makefile@1.22
/
diff
pkgsrc/archivers/py-zstandard/distinfo@1.22 / diff
pkgsrc/archivers/py-zstandard/patches/patch-c-ext_backend__c.c@1.3 / diff
pkgsrc/archivers/py-zstandard/distinfo@1.22 / diff
pkgsrc/archivers/py-zstandard/patches/patch-c-ext_backend__c.c@1.3 / diff
py-zstandard: updated to 0.17.0
0.17.0 (released 2021-01-18)
Backwards Compatibility Notes
ZstdCompressionWriter and ZstdDecompressionWriter now implement __iter__() and __next__(). The methods always raise io.UnsupportedOperation. The added methods are part of the io.IOBase abstract base class / interface and help ensure instances look like other I/O types.
The HASHLOG3_MAX constant has been removed since it is no longer defined in zstd 1.5.1.
Bug Fixes
The ZstdCompressionReader, ZstdCompressionWriter, ZstdDecompressionReader, and ZstdDecompressionWriter types in the C backend now tracks their closed attribute using the proper C type. Before, due to a mismatch between the C struct type and the type declared to Python, Python could read the wrong bits on platforms like s390x and incorrectly report the value of the closed attribute to Python.
Changes
Bundled zstd library upgraded from 1.5.0 to 1.5.1.
The C backend now exposes the symbols ZstdCompressionReader, ZstdCompressionWriter, ZstdDecompressionReader, and ZstdDecompressionWriter. This should match the behavior of the CFFI backend.
ZstdCompressionWriter and ZstdDecompressionWriter now implement __iter__ and __next__, which always raise io.UnsupportedOperation.
Documentation on thread safety has been updated to note that derived objects like ZstdCompressionWriter have the same thread unsafety as the contexts they were derived from.
0.17.0 (released 2021-01-18)
Backwards Compatibility Notes
ZstdCompressionWriter and ZstdDecompressionWriter now implement __iter__() and __next__(). The methods always raise io.UnsupportedOperation. The added methods are part of the io.IOBase abstract base class / interface and help ensure instances look like other I/O types.
The HASHLOG3_MAX constant has been removed since it is no longer defined in zstd 1.5.1.
Bug Fixes
The ZstdCompressionReader, ZstdCompressionWriter, ZstdDecompressionReader, and ZstdDecompressionWriter types in the C backend now tracks their closed attribute using the proper C type. Before, due to a mismatch between the C struct type and the type declared to Python, Python could read the wrong bits on platforms like s390x and incorrectly report the value of the closed attribute to Python.
Changes
Bundled zstd library upgraded from 1.5.0 to 1.5.1.
The C backend now exposes the symbols ZstdCompressionReader, ZstdCompressionWriter, ZstdDecompressionReader, and ZstdDecompressionWriter. This should match the behavior of the CFFI backend.
ZstdCompressionWriter and ZstdDecompressionWriter now implement __iter__ and __next__, which always raise io.UnsupportedOperation.
Documentation on thread safety has been updated to note that derived objects like ZstdCompressionWriter have the same thread unsafety as the contexts they were derived from.