-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
add more detail on platform missmatch errors instead of just declaring not matching distributions found #5003
Comments
Heyo! Yeah. We should print the number of compatible distributions found by platform and all. I think there's an existing issue for this, or its mentioned in another issue somewhere. I don't have the time to look right now. =| |
Found it: #4649 (comment) Leaving this issue open to track the number of compatible releases "not selected" being printed. :) |
This error is misleading should be fixed. Please don't forget about this issue! |
@cowlinator - it’s only a year later, but I was looking for something to contribute and will be picking this up. :) |
Let’s make sure I understand this one. In the example above of The desired state then would be something like this:
If someone could review the above desired state I’d appreciate it. Once that’s confirmed I’ll figure out how to get the list of classifiers from the package and implement the change and associated tests. |
I don't think the classifiers should be involved (though I haven't looked at the internals) -- but I'd be almost positive pip's notion of what discovered distributions are applicable is some other internal state (one using $ pip install --user keyring_jeepney
Collecting keyring_jeepney
Could not find a version that is supported on your platform (CPython 3.6.3 on macOS)
Found 2 unsuitable binary distributions:
keyring_jeepney-0.3.2.whatever.whl ([in green]CPython3[endgreen] for [in red]Linux[endred])
keyring_jeepney-0.4.7.whatever.whl ([in red]PyPy[endred] for [in green]macOS[endgreen])
and no available source distribution. Others may pipe up with improvements/suggestions, but I think something like that is at least in the ballpark. And thanks again for trying to tackle this -- I think it'd be a big win (I can say anecdotally I probably have explained this specific error to >~20 people myself in #python). |
pip 9.0.1 python 2
got
expected
The text was updated successfully, but these errors were encountered: