-
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
pip --upgrade installs yanked version (only) with new resolver #9290
Comments
I have the same issue with problem 2 when update packages, not only pip, but any outdated packages, it will download all the versions of that package. |
Problem 2 is effectively #9284 and has nothing to do with yanked versions - my bad. Problem 1 remains. |
This is a known issue with 20.3.1. I don’t think 20.3.2 has this (#9226), and the above does not seem to demostrate the behaviour of 20.3.2 either. But 20.3.2 has other issues and can’t be used anyway, of course 🙂 |
I’ll close on the assumption #9226 fixes this. Feel free to reopen if 20.3.3 still has this issue. |
Correct! 20.3.2 should have been removed from my report when I removed my duplicate of #9284 - I can repro this only on 20.3.1. |
I will hardly know: once 20.3.3 is out, |
Good point… Let me produce a fake pip version before 20.3.3 is out. Edit:
This should be the same as 20.3.3, but with a version earlier than 20.3.2. |
Thank you! |
Environment
Description
As of today:
python -m pip install pip --force
installs20.3.1
, which I believe is correct.python -m pip install pip --upgrade
installs20.3.2
, which I don't understand why:20.3.2
is yanked, and https://pypi.org/help/#yanked says:But I did not use any version specifier, so why did it use that yanked version? Note that PEP 592 does not contain the word "upgrade".
Expected behavior
I think I would expect
python -m pip install pip --upgrade
to ignore yanked versions. Alternatively, the text at https://pypi.org/help/#yanked should be corrected.How to Reproduce
Output
This is an issue of the new resolver - the old one does not have this issue:
remains at
20.3.1
.The text was updated successfully, but these errors were encountered: