> You can then use tox (or nox) to define your component and framework versions as variant virtual environments. As components evolve, you update the versions and rerun your test suite. You can publish internal update trackers for project teams to make sure they're testing with the latest-and-greatest environments.
So I am curious about the specific tool recommendation, thus the question.
The bunfight about how those tool choices are made is in view.
In that sense, The Famous Article is not very python-specific.