'pip' isn't always the python we're running under #4920
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
Signed-off-by: Jason Short <jason.short@wpengine.com>
|
Unfortunately that would break our binary distribution (where I'm afraid you'll have to ignore the warning |
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.
On distributions that allow parallel python2 and python3 installation, the
pipbinary may not be the python we're running under. Specifically, we ran into a case where we needed docker-py in python2 to support a specific version of Ansible, and decided to install docker-compose via python3 pip to avoid a collision. Much to our chagrin, python3 docker-compose continued to complain about docker-py, because of its naive usage ofpip. And yes, I hear you when you say virtualenv.