if poetry is installed into a virtualenv, it's installing my project into it too

• I am on the latest Poetry version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: macOS 10.14

• Poetry version: 0.12.3

Issue

I have installed poetry into a virtualenv, and poetry is using that virtualenv to install my project, despite it not being active. I would expect poetry to make a new virtualenv for this project.

$ python3 -m venv penv
$ penv/bin/pip install poetry
$ penv/bin/poetry install

Note that my project was installed into penv despite it not being activated. It looks like (possibly) https://github.com/sdispater/poetry/commit/fa4c116213557579b1596f2ff0148f7865759ac6 broke things. poetry debug:info displays the virtualenv as the penv that poetry is installed into but my shell has no VIRTUAL_ENV var set.

[roee-allegro]

I am experiencing this issue with 0.12.17. The way to reproduce is slightly different than @mmerickel 's:

python3 -m venv penv
. penv/bin/activate
pip install poetry
poetry install
# pip freeze output contains the project's requirements

[mmerickel]

thanks @sdispater !