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

Error message when package isn't support by current python version leaves a lot to be desired #5915

Closed
alex opened this issue Oct 24, 2018 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR

Comments

@alex
Copy link
Member

alex commented Oct 24, 2018

Environment

  • pip version: 18.1
  • Python version: 2.7.15
  • OS: macOS mojave

Description

If you attempt to install a package with a requires-python that doesn't match your current Python, the error message is unclear.

Expected behavior

An error stating the package could not be installed because there was no matching version should be emitted.

How to Reproduce

  1. Create a virtualenv with Python<3.6
  2. pip install black
~ ❯❯❯ pip install black
Collecting black
  Could not find a version that satisfies the requirement black (from versions: )
No matching distribution found for black

However black exists, it just requires Python 3.6+

@cjerdonek cjerdonek added this to the Print Better Error Messages milestone Oct 24, 2018
@cjerdonek cjerdonek added the resolution: duplicate Duplicate of an existing issue/PR label Oct 25, 2018
@cjerdonek
Copy link
Member

Thanks for the report. I'm marking this as a duplicate since it's already known. See, for example:

(FWIW, I think this issue should be prioritized IMO.)

@lock
Copy link

lock bot commented May 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 31, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants