- 
                Notifications
    
You must be signed in to change notification settings  - Fork 383
 
Open
Description
I've got a workflow where I added a Brew install Step to install Python, which works well.
The next Step that runs after this is a Script Step that I use to run pip (one of the Python tools), in order to install a public plugin.
It contains something like this (I've added a generic name for the plugin, myPlugin):
python3 -m pip --version
python3 -m ensurepip --default-pip 
alias pip='pip3'
pip install myPlugin
The problem is that it always fails saying that it doesn't know what pip is (in the 4th line).
Surprisingly, if I run the workflow with Remote Access and I use the terminal to run the same commands it works. So I'm not sure what the issue is that is causing the pip command not being recognised.
Is this an issue known when it comes to work with Python and the package manager pip?
Metadata
Metadata
Assignees
Labels
No labels