Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup: don't use transition package as dependency #293

Merged
merged 1 commit into from
Jan 9, 2018
Merged

Setup: don't use transition package as dependency #293

merged 1 commit into from
Jan 9, 2018

Conversation

mhinz
Copy link
Member

@mhinz mhinz commented Jan 9, 2018

The official package was renamed to msgpack whereas msgpack-python still acts as a transition package for it.

Relevant commits:

@bfredl
Copy link
Member

bfredl commented Jan 9, 2018

As 0.5 is the first version with the new name, shouldn't it say msgpack>=0.5.0 ? Otherwise LGTM.

The official package was renamed to "msgpack" whereas "msgpack-python" still
acts as a transition package for it.

Relevant commits:

- msgpack/msgpack-python@89e4f8b
- msgpack/msgpack-python@9f4c12f
- msgpack/msgpack-python@5be9378
@bfredl bfredl merged commit 80428b1 into neovim:master Jan 9, 2018
@mhinz mhinz deleted the dep branch January 9, 2018 21:32
bfredl added a commit that referenced this pull request Feb 2, 2018
Adds compability with msgpack 0.5.2.

Changes since 0.2.0:

    e800c64 discover_runtime_directories refactor (#287)
    9cf971f Travis lint refactor (#288)
    93e6b5b msgpack-python was renamed to msgpack (#293)
    6fc0343 fix for msgpack 0.5.2 (#301)
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.

2 participants