Run scripts from the location they are saved in, instead of the destination of the softlink.

[masasin]

Feature description

When I run python, I use a virtual environment located inside the Tasker folder. However, the Python binaries there are actually softlinks to the system Python. Running them from inside the folder adds the virtual environment's packages to the python path, but running it from outside doesn't give you access to those packages.

Right now, when I need to run from inside a virtual environment, I import sys and add the library path to it. It happened so often that I just made a task that does that and pastes in the rest of the code into an empty file that I then run.

[agnostic-apollo]

Which version are you using?

Symlink file path is used instead of target path because some utils don't work if target path is used. Will have to add another option to disable the behaviour. I don't really understand your setup from the info provided to suggest alternatives.

https://github.com/termux/termux-tasker/blob/v0.6.0/app/src/main/java/com/termux/tasker/FireReceiver.java#L156

termux/termux-app@cce6dfe

[masasin]

I'm using 0.6.0.

This is my setup:

I have python installed system-wide, and I created a venv folder for tasker stuff because I don't want to install e.g. numpy or arrow globally.

If I run it directly (e.g., with -c "print('hello world')"), it does not have access to any of the packages in the venv. If I run it on a file, it's the same problem.

What I ended up doing is this:

Right before running anything, I add the venv path to the sys path.

Adding the toggle would make it possible to simplify things by allowing me to run certain things directly, but it works fine in this configuration too, so there's no rush for me.

[agnostic-apollo]

Why not just create wrapper script at ~/.termux/tasker/venv-exec and call that with plugin.

#!/usr/bin/bash

exec env VIRTUAL_ENV=~/.termux/tasker/venv python "$@"

https://stackoverflow.com/questions/48174599/is-there-a-single-line-way-to-run-a-command-in-a-python-venv

p.s I don't have any experience with python virtual environments.