Support msgpack 1.0.0

[pcdinh]

In msgpack 1.0.0, the default value of strict_map_key is changed to True to avoid hashdos. However, it will break the Tarantool driver, causing an exception:

ValueError: int is not allowed for map key

As a result, the driver is unable to parse server response. The issue is reported at #155

[Totktonada]

In CI:

TypeError: __init__() got an unexpected keyword argument 'strict_map_key'

It seems we should support both old and new implementations.

[Totktonada]

Please, squash commits and explain changes in the commit message (just like you did for the PR description). Don't forget to include Fixes #155 or Closes #155 tag.

See also the comment below.

[Totktonada]

We can reduce code duplication by unpacking a dictionary to keyword parameters. A kind of this (not tested):

kwargs = dict(use_list=True)
if msgpack.version >= (1, 0, 0):
    # XXX: Explain why it is necessary.
    kwargs['strict_map_key'] = False
if msgpack.version >= (0, 5, 2) and conn.encoding == 'utf-8':
    # Get rid of the following warning.
    # > PendingDeprecationWarning: encoding is deprecated,
    # > Use raw=False instead.
    kwargs['raw'] = False
elif conn.encoding is not None:
    kwargs['encoding'] = conn.encoding

unpacker = msgpack.Unpacker(**kwargs)

[Totktonada]

From python-msgpack 1.0.0 release notes:

• Remove encoding option from the Packer and Unpacker.

Are'we affected by this?

[Totktonada]

From python-msgpack 1.0.0 release notes:

• Remove encoding option from the Packer and Unpacker.

Are'we affected by this?

In fact, no:

I dived a bit further and it reminds me changes we did for msgpack-0.5.2.

We already use raw=False when encoding is 'utf-8' since msgpack-0.5.2 (2097884), because otherwise it emits the deprecation warning regarding encoding option usage. So we should just continue passing raw=False on msgpack-1.0.0.

[Totktonada]

Closed in favor of PR #173.