-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Confusing pip behavior when trying to install a package with an outdated Python version #7797
Comments
This is essentially a special case to #6526. Probably could be marked as duplicate. |
Indeed, you are correct. With The discussion of the issue you linked is quite long, I'm not sure what is the status. |
The state is everyone agrees this needs fixing, but not quite sure how. A pull request to prototype the implementation would be quite useful IMO, if someone’s willing to do it. |
Switching from a pip/src/pip/_internal/index/package_finder.py Lines 89 to 92 in 520e76d
|
The message probably needs some rewording as well; I’d imagine people be confused unless they are already familiar with how the package index works. Feel free to work on this. |
We definitely want something smarter than that. Otherwise, we'd go from (using Python 2):
to
I think something based on #6119 to easily output the useful information when needed would be a better direction. |
I have just recreated this issue with python 3.6.15 and pip 21.3.1 on Manjaro 22.0.0. I installed my own test package (requiring python 3.6) and tried to upgrade to a new version of said package requiring python 3.7. The following error message was generated:
Based on this result I'd say that the underlying issue was fixed. |
Hello,
Environment
Description
I have Python 3.5, and wanted to upgrade Matplotlib version from 3.0.3 to 3.1.3. I just found out that it requires Python 3.6, but Pip never told me that, and its behavior was very confusing (no message of any kind).
Expected behavior
I think that Pip should tell the user why a specific version can not be installed when the requirements are not satisfied. Or at least have a generic message like "If you believe this package/version does exist, check that your installation fulfill the package requirements from its setup.py file".
How to Reproduce / Output
Have Python <3.6 (for ex 3.5), and run:
The text was updated successfully, but these errors were encountered: