python-msgpack
No description set
- Sources inherited from project devel:languages:python
- Devel package for openSUSE:Factory
-
14
derived packages
- Links to openSUSE:Factory / python-msgpack
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:Maliku:python/python-msgpack && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
msgpack-0.6.1.tar.gz | 0000118812 116 KB | |
python-msgpack.changes | 0000008552 8.35 KB | |
python-msgpack.spec | 0000002451 2.39 KB |
Revision 16 (latest revision is 39)
Ondřej Súkup (mimi_vx)
committed
(revision 16)
- update to 0.6.1 * unpackb(data) configures max_*_len options from len(data), instead of static default sizes. * Unpacker(max_buffer_len=N) configures max_*_len options from N, instead of static default sizes. * max_bin_len, max_str_len, and max_ext_len are deprecated. * unpacker: Default value of input limits are smaller than before to avoid DoS attack * Unpacker doesn't wrap underlaying ValueError (including UnicodeError) into UnpackValueError. If you want to catch all exception during unpack, you need to use try ... except Exception with minimum try code block. * PackValueError and PackOverflowError are also removed. You need to catch normal ValueError and OverflowError. * Unpacker has strict_map_key option now. When it is true, only bytes and str (unicode in Python 2) are allowed for map keys. * Extension modules are merged. There is msgpack._cmsgpack instead of msgpack._packer and msgpack._unpacker. * Add Unpacker.getbuffer() method. * unpacker: msgpack.StackError is raised when input data contains too nested data * unpacker: msgpack.FormatError is raised when input data is not valid msgpack format.
Comments 2
Could you keep Version 1.0 in devel and don't submit it to openSUSE:Factory ? borgbackup doesn't support this version.
https://github.com/borgbackup/borg/issues/5065
Somebody suggested there using bundled version of msgpack. I think as a temporary solution until this bug is fixed, it could work well enough.