DRAFT
This issue is for write down my ideas.

Changing default behavior to use new spec.

See also: https://github.com/msgpack/msgpack/blob/master/spec.md#upgrading-messagepack-specification.

v1.0

Drop encoding and unicode_errors option in Unpacker. Add raw=False option instead. When raw=True is passed, raw data in msgpack is deserialized into bytes object.

Drop encoding and unicode_errors option in Packer. Unicode is encoded with UTF-8 always.
'surrogatepass' is not allowed to keep generated msgpack clean. use_bin_type=False is the only way to create dirty (raw contains non UTF-8 data) msgpack.

v0.5.x

Add raw=True option to unpacker.

v0.6

0.6 is version for warnings.

Packer warns when encoding or unicode_errors is specified.

Unpacker warns when encoding or unicode_errors is specified. ("Use raw=False instead").

PyPI package name

In past, easy_install crawls msgpack website and finds msgpack-x.y.z.tar.gz. But it was for C.
That's why I moved from msgpack to msgpack-python

Sadly, pip doesn't support transitional package (empty, but depends on new name package).
So I release msgpack as both of msgpack-python and msgpack for a while until 1.0.

As 1.0, I release msgpack only.