Option to force Poetry to create a virtual environment, even if a virtual env is active

I am using Poetry from within a conda environment; with Poetry being installed by conda (poetry is present in the environment.yaml file). This might not be ideal but for a specific setup this seems to work well.

When running poetry install, a venv is not created because Poetry detect that a virtual environment (the Conda one) is already active.

I believe that we should be able to force Poetry to create a virtual environment anyway: the Conda environment is more "physical" than virtual in this case, as it replaces the system Python.

The same issue occurs when doing poetry shell from within the Conda environment, after creating the virtual environment with the following workaround: I deactivate the Conda environment, use the full path to Poetry (in the bin directory of the Conda environment) and do poetry install.

Start by tracing how poetry install and poetry shell detect an already-active Conda environment, then review the existing virtual-environment configuration behavior. Define how a force option should apply to both commands, and consider the work complete when an active Conda environment no longer prevents Poetry from creating and using its own virtual environment.