Closed maxrake closed 1 year ago
This alone didn't seem to fix it on my end. My machine only has pip
at pip3
. I'm not sure if this is standard on MacOS, but I don't believe I've installed it separately. Changing all references of pip
to pip3
did seem to fix it with these changes though.
We should consider updating the UX here, such that a failure to find pip
explicitly states that pip could not be found.
This alone didn't seem to fix it on my end. My machine only has
pip
atpip3
. I'm not sure if this is standard on MacOS, but I don't believe I've installed it separately. Changing all references ofpip
topip3
did seem to fix it with these changes though.We should consider updating the UX here, such that a failure to find
pip
explicitly states that pip could not be found.
Well...this just got more complicated...more than I can handle, anyway, in a reasonable time frame. I can close this PR or have @cd-work take it over.
The other part of the solution for getting this extension working is in #21
We should consider updating the UX here, such that a failure to find
pip
explicitly states that pip could not be found.
This is related to https://github.com/phylum-dev/cli/issues/781, which is a CLI issue. This community extension PR can proceed without this fix for now.
This PR adds another, default, location on macOS for where the
python
binary can live.