Skip to content

Use new msgpack spec by default. - #386

Merged
methane merged 6 commits into
msgpack:masterfrom
methane:msgpack-2.0
Dec 5, 2019
Merged

Use new msgpack spec by default.#386
methane merged 6 commits into
msgpack:masterfrom
methane:msgpack-2.0

Conversation

@methane

@methane methane commented Dec 5, 2019

Copy link
Copy Markdown
Member

Fixes #99

@methane
methane merged commit 7e9905b into msgpack:master Dec 5, 2019
@methane
methane deleted the msgpack-2.0 branch December 5, 2019 12:34
Comment thread README.rst
object into raw type in old msgpack spec, instead of bin type in new msgpack spec.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo

Comment thread test/test_case.py

def test_unicode():
assert unpackb(packb("foobar"), use_list=1) == b"foobar"
assert unpackb(packb(u"foobar"), use_list=1) == u"foobar"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

somehow makes more sense now. \o/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unpack should decode string types by default

2 participants