Using a different virtualenv for nested projects

[sezanzeb]

I set up a project to reproduce this: https://github.com/sezanzeb/nested-poetry-example

I want to run the nested project in a different virtualenv, while I am inside the virtualenv of the root project.

• Enter the virtualenv (python3 -m poetry run bash)
• Run code in the subfolder, which has its own pyproject.toml and a different virtualenv

The current behavior is, that it won't change the virtualenv. I don't know if this is expected, or a bug. I tried setting the -P and -C options, but they didn't change it. I would have expected -P to work.

I'll create a proper issue, unless what I'm doing is some odd out-of-scope stuff.

Currently I can get it to work by unsetting the VIRTUAL_ENV environment variable, but I don't know if this is actually a stable solution for the future. Using source deactivate works as well.

Issue boils down to, I guess: -P doesn't work when already in a virtualenv.

[sezanzeb]

https://github.com/python-poetry/poetry/blob/main/src/poetry/utils/env/env_manager.py#L216 The difference is, that in_venv is True because VIRTUAL_ENV is set, which causes return VirtualEnv(os.environ["VIRTUAL_ENV"])

There could maybe be a check that sets in_venv to False if VIRTUAL_ENV does not match the env of the project passed via -P. is_in_correct_env = something something

[sezanzeb]

Possibly related: #2056