Vendor pip 22.0.3 followup changes #4968
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e lock process working again with the right versions, but the hashes are in fact missing still.
…. Want to see if the CI tests pass with this.
|
Did not realize the CI runs when pointing at any branch, which means I duplicated this PR. Closing this one in favor of the one that shows just the diff of changes: #4969 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a branch off my branch where I got the pip 22.0.3 vendoring working: #4966
I made a new branch for this because I realize I am not to change pip internals, but yet trying to get the locking working again.