poetry creates virtualenv with newer python rather than using existing env

• I am on the latest Poetry version.

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

• OS version and name: macOS

• Poetry version: 1.0.5

• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/cjw296/c60c14f105b24f3ca625a11c87789fa6

Issue

I’ve seen this across linux and mac, steps roughly as follows:

• my project has python = "^3.7"
• I run poetry shell which creates a virtualenv, ansible-config--DcQW89x-py3.7/ in this case.
• I do lots of setup, installation, use the env, months pass…
• I install a new version of Python on the machine (3.8 in this case)
• The next time I run poetry shell, rather than using the existing env, it creates a new, empty one, ansible-config--DcQW89x-py3.8/.

This should not happen, the existing environment should be used.

[MattiooFR]

I actually have the same problem, but without changing my version of python. I don’t know why but it seems randomly poetry will forget the path of the previously created venv and will create a new empty one, quite annoying…

[finswimmer]

Hello again,

poetry expects in first place that the venv uses the same python version as the to whatever the python binary links to. Beside the way I explained above, another solution is to set virtualenvs.in-project to true. This will create the venv within you project folder and poetry will recognize it at first place.