Pip is not required on osx #101
Open
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: Trent Mohay <[email protected]>
rain-on
force-pushed
the
tmm/remove_pip_for_osx
branch
from
719604e to
000446a
Compare
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.
scripts/acceptance.sh expects a number of core utils to be available on the system.
This includes "pip" (the python package manager).
On an OSX host, the pip package is installed as part of the python3 installation (via homebrew) - however no system-command is created to access it.
However, once inside a virtual-environment pip is available, as the module is wrapped by the
<venv>/bin/pipscript.