The virtualenv behind your tox environments will always reflect the
dependencies at the time of running. Never use tox --recreate again.
When testing or developing you may be updating or adding dependencies in the
tox.ini or requirements.txt files. You may then be stashing those changes
because they were bad. You may be switching between branches that have
different dependencies. Each time you do this, you need to recreate the tox
virtualenv so that those dependencies are correctly installed. Running tox --recreate does this by deleting that virtualenv and starting fresh.
When tox-auto-env is installed, virtualenvs created by tox are identified by
a hash of the dependencies that are installed in it. i.e. if you have 2
branches with different dependencies, running tox on each of those branches
will create 2 separate virtualenvs that will be used for those 2 branches.
tox-auto-env is a tox plugin. Use pip install tox-auto-env to install.
If installed correctly, it should show up when tox --version is run.
Inspired by tox-battery