Unable to Use Poetry Python Virtualenv

[ProfessorManhattan]

• Task version: 3.9.0
• Operating System: Ubuntu 20.04

I posted a similar issue before but never really found an answer. I am wondering how people are handling creating/using Python virtualenvs. In the example below, I attempt to source a bin/activate but I always get a 127 exit code. In other scenarios where I am successfully getting virtualenvs to source properly, the virtualenv is not maintained since every command seems to be in a new sub-shell and virtualenv requires that it be sourced when a shell first starts. This issue also means that if I have a bash function shared across two tasks, I have to include the function in both tasks since they are different sub-shells. Just wondering what other people are doing to get past these issues..

Example Taskfile showing the issue

---
version: '3'

tasks:
  one:
    cmds:
      - task: two
      - pip3 install ansible

  two:
    interactive: true
    label: three
    desc: Hey
    cmds:
      - poetry env info --path
      - . "/home/hawkz/.cache/pypoetry/virtualenvs/hawkz-iL5HU4tf-py3.9/bin/activate"

[andreynering]

Hi @ProfessorManhattan,

I converted this issues into a discussion as it's not exactly a bug.

---

I don't do Python so it's not trivial for me to try to help you.

I suppose that if you run it before every command that would work.

I think it'd be interested at #204 which tries to solve use cases like this.

[ssbarnea]

That is simple and would break any environment manager tool, including python virtualenv, likely rbenv and nvm too.

Each command entry under cmds list is a standalone shell, so it will inherit nothing from the previous command, so basically you will not have the virtualenv activated,

The workaround is to write an entire shell script as a single command:

cmds:
  - |
    activate
    echo 123
    ...