Pipenv cannot install packages, suggested workaround doesn't work either
See original GitHub issueI have a simple little project with three dependencies: Flask, Flask-Cors and requests. My Pipfile lists the version for each as “*”, since I want to stay up to date and just use the newest version anyway.
When I run pipenv install, I get the following error:
Could not find a version that satisfies the requirement Flask
(from -r /tmp/requirements.txt (line 3)) (from versions: )
No matching distribution found for Flask (from -r /tmp/requirements.txt (line 3))
along with the suggestion to use --ignore-hashes
to get around this.
However, using the option gives the exact same behavior.
This happens on Ubuntu 16.10, Xubuntu 16.04, and Manjaro Linux.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
pipenv install -e . fails due to dependency resolution ... - GitHub
First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again. Alternatively, you can use $ pipenv ......
Read more >pipenv install packages for python is not working
There is your answer. The Scripts directory with utility scripts for packages installed per-user is not on PATH , so your command shell...
Read more >Common Pipenv Errors and How to Solve Them: Why Won't it ...
Here, you'll learn how to troubleshoot Pipenv installation and locking issues. ... Pipfile won't lock when it tries to install packages that don't...
Read more >Frequently Encountered Pipenv Problems - Read the Docs
This is usually a result of mixing Pipenv with system packages. We strongly recommend installing Pipenv in an isolated environment.
Read more >pipenv Documentation - Read the Docs
This tutorial walks you through installing and using Python packages. It will show you how to install and use the necessary tools and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The hash thing was definitely a faux pas on our part. I’ve pushed db4a181 to address this so we’re not leading people astray with erroneous error messages. That’s probably the best we can do at this point. Hopefully this issue will help anyone else hitting this issue. Thanks for your time working through this 😃
Thank you for your effort!
I sure hope others will benefit too. It was a weird and frustrating error for me^^