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

pip can't find tensorflow, amongst other dependencies, even though they exist #7565

Closed
Frontear opened this issue Jan 7, 2020 · 4 comments
Closed

Comments

@Frontear
Copy link

Frontear commented Jan 7, 2020

Environment

  • pip version: 19.3.1
  • Python version: 3.8.1
  • OS: Manjaro, with Kernel 54

Description
pip is unable to find a matching version of tensorflow, even though said versions can be found and manually downloaded from pypi. It's becoming quite frustrating to have to manually download the wheel packages and install them.

Expected behavior
pip should be able to find and download the libraries

How to Reproduce

  1. Run any shell environment
  2. Execute pip install tensorflow==1.15.0
  3. Errors will follow, specifically that it can't find the versions, although it can be browsed here

Output

ERROR: Could not find a version that satisfies the requirement tensorflow==1.15.0 (from versions: none)
ERROR: No matching distribution found for tensorflow==1.15.0

Edit

On consideration, my issue is far more likely due to the fact that I'm on a very new version of python, and as such, pip can't find a compatible package for my current version.

@triage-new-issues triage-new-issues bot added the S: needs triage Issues/PRs that need to be triaged label Jan 7, 2020
@Frontear
Copy link
Author

Frontear commented Jan 7, 2020

After even further consideration, I realized my amateur mistake. My version of python was simply too new for pip to find any compatible packages. As such, it specified the error.

However, I have a suggestion in that regard. pip should instead explicitly state that the version of python is too new/old, so as to reduce confusion.

Edit

For any future reference, since manjaro would totally break should I try to downgrade python, my only solution was to use pyenv, and install an older version of python.

@uranusjr
Copy link
Member

uranusjr commented Jan 7, 2020

You’re not alone. And the mistake is not amateur at all—even experienced developers need some time to process what’s going on when it happens, the message could use a lot of improvements :)

The issue is most broadly tracked in #4649, with several more specific areas that should be worked on.

@vorburger
Copy link

#4228, #6526 and #8831 are more narrow issues than #4649 that this issue could perhaps be duplicated to.

@uranusjr
Copy link
Member

I’m going to just close this in favour of #10421. This specific error message comes from the legacy resolver and is not going to be improved upon. The newer issue provides more relevant context toward the issue in its current state, against the current resolver implementation.

@uranusjr uranusjr closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 25, 2022
@pradyunsg pradyunsg removed the S: needs triage Issues/PRs that need to be triaged label Mar 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants