Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUse new msgpack spec by default. #386
Conversation
|
|
||
| In case of packer, use UTF-8 always. Storing other than UTF-8 is not recommended. | ||
| You can unpack old msgpack formatk using ``raw=True`` option. |
| @@ -135,4 +134,4 @@ def test_match(): | |||
|
|
|||
|
|
|||
| def test_unicode(): | |||
| assert unpackb(packb("foobar"), use_list=1) == b"foobar" | |||
| assert unpackb(packb(u"foobar"), use_list=1) == u"foobar" | |||
ThomasWaldmann
Dec 5, 2019
Contributor
are there enough tests that check all "old msgpack" behaviour as well as all "new msgpack" behaviour (str, bytes, unicode).
esp. that using it the old way still works with the new code, when the right options are given.
borgbackup depends on old format and as people have that in their backup repositories, we can't change it.
Fixes #99