-
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 --use-deprecated legacy-resolver download ...
fails at b88addeaf5fde848733d7ef631caa522eb1cfa53
#12138
Closed
1 task done
Labels
type: bug
A confirmed bug or unintended behavior
Comments
jsirois
added
S: needs triage
Issues/PRs that need to be triaged
type: bug
A confirmed bug or unintended behavior
labels
Jul 11, 2023
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Jul 11, 2023
A recent Pip commit has broken `pip --use-deprecated legacy-resolver download ...` which is our backwards-compatible default use case. Whether or not Pip decides to fix, the legacy resolver will be yanked at some point and it seems reasonable to just require any Pex user on Python 3.12 and thus Pip 23.2 to only use the Pip 2020 resolver. See: pypa/pip#12138
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Jul 11, 2023
A recent Pip commit has broken `pip --use-deprecated legacy-resolver download ...` which is our backwards-compatible default use case. Whether or not Pip decides to fix, the legacy resolver will be yanked at some point and it seems reasonable to just require any Pex user on Python 3.12 and thus Pip 23.2 to only use the Pip 2020 resolver. See: pypa/pip#12138
I have another finding that |
jsirois
added a commit
to pex-tool/pex
that referenced
this issue
Jul 11, 2023
A recent Pip commit has broken `pip --use-deprecated legacy-resolver download ...` which is our backwards-compatible default use case. Whether or not Pip decides to fix, the legacy resolver will be yanked at some point and it seems reasonable to just require any Pex user on Python 3.12 and thus Pip 23.2 to only use the Pip 2020 resolver. See: pypa/pip#12138
Thanks for the fix @uranusjr. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I bisected to b88adde (#11945) using:
The error is:
Expected behavior
No backtrace / blowup or else removal of
--use-deprecated
support forlegacy-resolver
as per: https://pip.pypa.io/en/latest/user_guide/#deprecation-timelinepip version
unreleased: main @ b88adde
Python version
3.12 (but same with others)
OS
Linux (Ubuntu 22.04)
How to Reproduce
See above, but in a pypa/pip clone:
Output
Code of Conduct
The text was updated successfully, but these errors were encountered: