Follow

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use
Contact

Solving a pip issue using a range vs removing package range altogether

I’m getting a conflict with a pip install and I get this message:

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

So if I have, let’s say:

pandas==1.1.2

I could put:

MEDevel.com: Open-source for Healthcare and Education

Collecting and validating open-source software for healthcare, education, enterprise, development, medical imaging, medical records, and digital pathology.

Visit Medevel

pandas>=1.1.0,<1.1.4

But would using:

pandas

simply look through all possibilities and fix it itself?

I’m not sure If I’m being clear, but basically, if I don’t care about version number, can I just use no versions as a better solution, because it would implicitly go through the all the ranges?

>Solution :

While this might fix your issue as @linger1109 suggested, it is highly recommended to specify a version number in your dependency manifest (e.g. requirements.txt.

There is no guarantee that future versions of pandas are fully backwards compatible, meaning the next time you install your dependencies, pip might opt for a newer version of pandas, potentially breaking your code.

I’d suggest finding versions of dependencies that are compatible with each other and declaring them in your dependencies manifest.

Add a comment

Leave a Reply

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use

Discover more from Dev solutions

Subscribe now to keep reading and get access to the full archive.

Continue reading