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

Conflicts between iprange-python and redis #1

Open
NeolithEra opened this issue Dec 9, 2019 · 2 comments
Open

Conflicts between iprange-python and redis #1

NeolithEra opened this issue Dec 9, 2019 · 2 comments

Comments

@NeolithEra
Copy link

Hi, users are unable to run iprange-python due to dependency conflict with redis package. As shown in the following full dependency graph of iprange-python, iprange-python requires redis >=2.10.6,while redis-py-cluster requires redis <3.1.0,>=3.0.0.

According to pip’s “first found wins” installation strategy, redis 3.3.11 is the actually installed version. However, redis 3.3.11 does not satisfy <3.1.0,>=3.0.0.

Dependency tree-----------

iprange-python - 0.0.8
| +- netaddr(install version:0.7.19 version range:>=0.7.19)
| +- redis(install version:3.3.11 version range:>=2.10.6)
| +- redis-py-cluster(install version:2.0.0 version range:>=1.3.4)
| | +- redis(install version:3.0.1 version range:<3.1.0,>=3.0.0)

Thanks for your help.
Best,
Neolith

@NeolithEra
Copy link
Author

Suggested Solution

  1. Ask your upstream project redis-py-cluster to upload a newer release on PyPI..
  2. Remove your direct dependency redis, and use redis transitively introduced by redis-py-cluster.

@NeolithEra lucasrodcosta Which solution do you prefer, 1 or 2?
Please let me know your choice. I can submit a PR to solve this issue.

@lucasrodcosta
Copy link
Owner

Thanks you so much for reporting this issue, @NeolithEra!

I prefer solution 2, and your PR will be very appreciated.

NeolithEra added a commit to NeolithEra/iprange-python that referenced this issue Dec 13, 2019
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

No branches or pull requests

2 participants