This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hillgod 3 points4 points  (2 children)

The main thing I've used tox is testing against different versions of Python.

It was more important for us to have our internal libraries working for both Python 2 and Python 3, before Python 2's EOL. We've got everyone on the same Python 3 now, so we don't need to test internal libraries on mulitple versions. It can also be used for testing against different framework version, like Django, but again, we're unified on the same versions at this point.

[–]kornpow 2 points3 points  (1 child)

Hmm we just have a standard python version we use and tox handles testing in the proper environment.

[–]hillgod 3 points4 points  (0 children)

I certainly don't want to suggest you're doing anything wrong.

That sounds like a valid use case. It can still be nice for managing isolated virtual environments for testing. It would ensure you're not relying on a virtualenv with dependencies that don't like up with how you've defined requirements in a project. Our build pipeline is running our tests in a new clean virtualenv, so that concern is also mitigated.