Support for multiple virtual environments (tox)

If I’m maintaining a package that needs to run under multiple python versions, I’d like to be able to pipenv install multiple times, so that I can do: pipenv run --python=python2.7 py.test tests or pipenv run --three py.test tests or ->

Tox. I copied and edited tox.ini from here http://docs.pipenv.org/en/latest/advanced.html#tox-automation-project but all the tests in every tox instance were running under the virtualenv of pipenv, instead of it’s own created one. So I went ‘oldschool’ with tox, running outside of pipenv, but it’s a shame it doesn’t work as the docs say.

[kennethreitz]

maybe make pipenv --two actually change the current virtualenv, and two are created, one for two, one for three!

[djetelina]

Well okay, that way tox could probably run, but instead of making my life easier, pipenv is actually making my life harder that way.

I’m not really sure if it should be tox recognizing pipfile and filling in dependencies from there, or pipenv being able to run tox, or if the way it is right now is okay.