fix upgrading pip to v10 #46
Merged
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
|
Thanks! |
lelit
added a commit
to python-rapidjson/python-rapidjson
that referenced
this pull request
Apr 25, 2018
oconnor663
added a commit
to buildinspace/peru
that referenced
this pull request
Jul 18, 2018
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.
Installing with
--useroption will leave the old pip.exe script in the $PATH, but then running the latter fails because pip 10 has moved its 'main' function to internal modules, and the old pip.exe launcher fails to import it.The fix is to force overwriting the old pip.exe by installing globally without the
--useroption.pypa/pip#5240 (comment)
Also see google/brotli#663