-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Downgrade and upgrade: cannot import name 'SourceDistribution' #8160
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
That's a known issue with pip 20.0 (which was a broken release) -- see #7620. |
Good to hear, I guess this can be closed then :) I just picked 20 out of the air because I wanted to downgrade from my local dev install, and upgrade to the new release. |
Now that PyPI has support for yanked releases, I've gone ahead and marked pip 20.0 as "yanked". This results in installing it via
|
Thanks @hugovk for the detailed bug report that made it easy to identify why this was happening! With 20.0 yanked, I think I can go ahead and close this now. :) |
You're welcome, and thanks!
Can you provide a reason at PyPI? Perhaps something along the lines of "20.0 is a broken build, use >=20.1 instead"? $ python3.6 -m pip install pip==20
WARNING: The candidate selected for download or install is a yanked version: 'pip' candidate (version 20.0 at https://files.pythonhosted.org/packages/60/65/16487a7c4e0f95bb3fc89c2e377be331fd496b7a9b08fd3077de7f3ae2cf/pip-20.0-py2.py3-none-any.whl#sha256=eea07b449d969dbc8c062c157852cf8ed2ad1b8b5ac965a6b819e62929e41703 (from https://pypi.org/simple/pip/) (requires-python:>=2.7,!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*))
Reason for being yanked: <none given>
Collecting pip==20
Using cached pip-20.0-py2.py3-none-any.whl (1.5 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 20.1
Uninstalling pip-20.1:
Successfully uninstalled pip-20.1
Successfully installed pip-20.0 |
Nope. :( |
Environment
Description
Expected behavior
Upgrades smoothly after downgrade.
How to Reproduce
Output
Can recover with
get-pip.py
:The text was updated successfully, but these errors were encountered: