Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
inconsistent version for every package
See original GitHub issueDescription
Running python -m pip install <any package> results in pip trying to downgrade versions until it runs out of them, thinking the metadata is in conflict even though they are of the same version in the error message.
Tried reinstalling python + pip on my Arch x64 already, issue persists for every package
Expected behavior
pip should install a package successfully
pip version
pip 21.0 from /usr/lib/python3.10/site-packages/pip (python 3.10)
Python version
Python 3.10.2
OS
Arch Linux
How to Reproduce
python -m pip <any package>
Output
https://asciinema.org/a/bKM5F5PidbwktgRXoEUqGbR2u
Code of Conduct
- I agree to follow the PSF Code of Conduct.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@TomasDrozdik indeed it was some weird env edge-case, although I didn’t tinker anything with the default arch python-pip installation on my new machine. My solution was:
Fair enough, I’ll try to reinstall it.