pipenv install --two always deletes virtualenv

I want to make a small script that automates running something that needs python2 with pipenv. I would do:

pipenv install --two
pipenv run hello.py

The first invocation is fine, the second time I run this script however it says:

Virtualenv already exists!
Removing existing virtualenv...
Creating a virtualenv for this project...

even though nothing has changed. It’s the --two option that causes this. If I remove that option it behaves as I would expect and reuses the old virtualenv, however then I get python3.

Since python3 is the default you don’t need --two/–three, so then you don’t have this problem.

[audiolion]

I guess what I wanted to happen was say pipenv install on my CI server and have a way to ensure it chooses the correct version of python, if the env didnt exist it might grab the system version first because it finds it on the path first, which is bad, but if a virtualenv already exists with that version, I don’t want it to destroy it. With the existing behaviors I am not sure how to make that happen.

[iandanforth]

I’d like to second the intuition that even explicit arguments won’t repeat work unnecessarily.