You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had a couple of situations where I wanted to run commands with a different interpreter than mvdan.cc/sh/v3/cmd/gosh. Two examples are:
Small python snippets that I want executed with the python interpreter:
tasks:
_rimraf:
# This task is a utility task for recursively removing directories, it is# similar to rm -rf but not identical and it should work wherever there is# a python interpreter. The name is inspired by# <https://www.npmjs.com/package/rimraf>.
- cmd: | {{.PYTHON}} -c ' from pathlib import Path; import sys, shutil; for path in sys.argv[1:]: if Path(path).exists(): sys.stderr.write(f"removing {path}\n") shutil.rmtree(path, ignore_errors=True) ' {{.RIMRAF_TARGET}}
I feel these two cases would be a bit more elegant if I could specify the interpreter separately from the command without having to pass the command as either an environment variable or a shell escaped string.
This is a rather minor request though, clearly there are serviceable workarounds that get the job done, but having something similar to the interpreter setting from poethepoet may help.
The text was updated successfully, but these errors were encountered:
@aucampia Thanks for opening this. I couldn't find the issue when you asked on Discord, but now that I've had more time to search, I think this is a duplicate of #448. I'm going to post my response over there and close this. If you and @Hades32 could add a 👍 and any comments over there too, that would help keep everything together.
I have had a couple of situations where I wanted to run commands with a different interpreter than
mvdan.cc/sh/v3/cmd/gosh
. Two examples are:Small python snippets that I want executed with the python interpreter:
Commands I want to execute on a LXD container:
I feel these two cases would be a bit more elegant if I could specify the interpreter separately from the command without having to pass the command as either an environment variable or a shell escaped string.
This is a rather minor request though, clearly there are serviceable workarounds that get the job done, but having something similar to the interpreter setting from poethepoet may help.
The text was updated successfully, but these errors were encountered: