tox and poetry both create their own venvs

[laurentS]

It looks like using both poetry and tox ends up creating multiple virtual envs for no useful reason, so all dependencies are installed twice, which seems a bit of a waste.

Maybe there is a way to make them aware of each other so that tox can reuse the poetry venv, or the other way around?

[aaronsteers]

@laurentS - I've run into this also, and I've experimented on a couple options with moderate success.

As I understand it, Tox prioritizes multiple builds in separate python versions, which limits the reusability of a single Poetry env.

I believe the SDK example does reuse the poetry env but my memory is rusty on this.

In case it is helpful:

• https://gitlab.com/meltano/sdk/blob/main/tox.ini