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

remove msgpack pin #818

Merged
merged 1 commit into from
Apr 11, 2020
Merged

Conversation

prometheanfire
Copy link
Contributor

The hard lock prevents this from being co-installed with many other
packages. For instance, it's preventing it from being included in
openstack (which is on 0.6.2 and working on 1.0.0 now).

Signed-off-by: Matthew Thode mthode@mthode.org


Contributor checklist
  • Builds are passing
  • [×] New tests have been added (for feature additions)

The hard lock prevents this from being co-installed with many other
packages.  For instance, it's preventing it from being included in
openstack (which is on 0.6.2 and working on 1.0.0 now).

Signed-off-by: Matthew Thode <mthode@mthode.org>
Copy link
Contributor

@sebito91 sebito91 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for adding!

@sebito91 sebito91 merged commit cc41e29 into influxdata:master Apr 11, 2020
ocworld pushed a commit to AhnLab-OSS/influxdb-python that referenced this pull request Apr 13, 2020
The hard lock prevents this from being co-installed with many other
packages.  For instance, it's preventing it from being included in
openstack (which is on 0.6.2 and working on 1.0.0 now).

Signed-off-by: Matthew Thode <mthode@mthode.org>
@cdessez
Copy link

cdessez commented Apr 14, 2020

Thanks for merging this fix!

Could we get a new 5.3.1 release for this? Currently the latest release of influxdb does not contain the fix and I have to pin it to get my CI pipeline to pass.

Cheers

@tiltec tiltec mentioned this pull request Jul 12, 2020
derekpierre added a commit to derekpierre/nucypher-monitor that referenced this pull request Sep 10, 2020
There is an issue with influxdb 5.3.0 and msgpack that we are avoiding for now (influxdata/influxdb-python#818).
When influxdb 5.3.1 becomes available we should switch to it.
@henningway
Copy link

Thanks for the fix! +1 on tagging a version. We get constant pip error messages because of the version conflict.

@nemesifier
Copy link
Contributor

+1 for a new minor release to fix this

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

Successfully merging this pull request may close these issues.

5 participants