[Feature request] Activating conda/virtualenv environments on xfunc


It would be important to be able to specify which environment needs to be activated when calling an XFunc.


hi gonzalo,

which command do you currently use to activate a virtual environment? something like:

source path/to/my/venv/bin/activate



It depends on the virtual environment manager and on the OS.

Using conda is:

  • Windows: activate myenv
  • mac / linux: source activate myenv

(where myenv is env name, not path)

But using virtualenv is a tad different (\path\to\env\Scripts\activate and source path/bin/activate on Win and Mac/Linux respectively). And using Pipenv is again different.

In any case, maybe it makes sense to go for the same approach gh-python-remote uses, it already works with conda and without: