Recreating virtualenv when python_version changes instead of warning

When the “python_version” in a Pipfile changes I get warnings but i manually have to run pipenv install --python X.X.

My understanding of the idea of pipenv is, that running pipenv update will sync my virtualenv with my Pipfile (without need for manual interaction). Thus: why is this not the case for changing the python version.

[uranusjr]

It is an anti-pattern (I’d even say it’s anti-pattern to virtual environment usages in general), but people still depend on the behaviour, and sometimes it is even a useful hack. Like it is also an anti-pattern to install packages with managing it with Pipfile (pipenv run pip install), but we still allow that for the occasional edge cases, only inteerfere when the user explicit wants us to (pipenv clean). It’s probably a good idea to follow the same pattern here, i.e. don’t actively overwrite (only showing errors), but provide a clear path to encourage it (with a command option, for example).

[kennethreitz]

i like the current implementation