Wow! I thought this was a regression, but on closer examination #tox
never supported automatically recreating the environment when requirements.txt changes.
The set of observations that go into the decisions whether to recreate a tox venv are:
- The tox version changed
- The python binary hash changed
- The list of deps changed, meaning *the text in tox.ini and the direct dependencies it refers to*
- The list of requirements for the provision_tox_env changed
- A few other things
When you put -r requirements.txt
, the contents of the file are not examined!
I'm probably not the only person who didn't realize that you need to tox -r
when you've changed the requirements.txt.
When I make changes to my project's requirements.txt and run tests, tox no longer picks up the change and so I must run it with tox -r first. This is for a django project (and we have no setup....github.com