-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script Step to run pip (python 3) #3487
Comments
Hey Fernando, have you tried skipping the alias and just calling |
Hey @matrangam I tried that already and didn't work. The next logs are showed after running the script with the alias included:
|
ok, that helps a little I think. |
I don't have the Step built yet. I was still playing around with the commands I will use in the Step. |
Hello @ferPrieto,
|
I've got a workflow where I added a
Brew install Step
to installPython
, 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):
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 thesame
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 managerpip
?The text was updated successfully, but these errors were encountered: