Skip to content
This repository was archived by the owner on Oct 29, 2024. It is now read-only.

use msgpack>=0.6.1 #830

Open
robin-xl opened this issue Jun 10, 2020 · 5 comments
Open

use msgpack>=0.6.1 #830

robin-xl opened this issue Jun 10, 2020 · 5 comments

Comments

@robin-xl
Copy link

this package use msgpack==0.6.1 in requirements.txt,it's possible to use msgpack>=0.6.1?
this may have a compatibility problem with other package ,e.g locust need msgpack>=0.6.2

@VeNoMouS
Copy link

VeNoMouS commented Jun 20, 2020

msgpack 1.0.0 is latest

1.0.0

Release Date: 2020-02-17

  • Remove Python 2 support from the msgpack/_cmsgpack.
    msgpack/fallback still supports Python 2.
  • Remove encoding option from the Packer and Unpacker.
  • Unpacker: The default value of max_buffer_type is changed to 100MiB.
  • Unpacker: strict_map_key is True by default now.
  • Unpacker: String map keys are interned.
  • Drop old buffer protocol support.
  • Support Timestamp type.
  • Support serializing and decerializing datetime object
    with tzinfo.
  • Unpacker: Fix Unpacker.read_bytes() in fallback implementation. (Data types #352)

0.6.2

Release Date: 2019-09-20

  • Support Python 3.8.
  • Update Cython to 0.29.13 for support Python 3.8.
  • Some small optimizations.

0.6.1

Release Date: 2019-01-25

This release is for mitigating pain caused by v0.6.0 reduced max input limits
for security reason.

  • 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.
    Since this is minor release, it's document only deprecation.

@tiltec
Copy link

tiltec commented Jul 12, 2020

This seems to be fixed in #818 already, but unpublished yet. Could someone publish a new version?

@mced
Copy link

mced commented Jul 15, 2020

@sebito91 any news on this ?

@amitwer
Copy link

amitwer commented Sep 29, 2020

Please note, using pip install --use-feature=2020-resolver (which is soon to become the default, as far as I understand) does result in breaking builds in case of a conflict, with no real way to resolve it

@VeNoMouS
Copy link

VeNoMouS commented Oct 3, 2020

Tagging @russorat to see if he can get some traction...

Sick of see'ing this warning on my builds..

ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.

We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.

influxdb 5.3.0 requires msgpack==0.6.1, but you'll have msgpack 1.0.0 which is incompatible.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants