On Fri, Jul 29, 2016 at 4:42 PM, Victor Stinner firstname.lastname@example.org wrote:
2016-07-29 20:51 GMT+02:00 Zachary Ware email@example.com:
I think rather than using virtual environments which aren't truly supported by <3.3 anyway, ...
What do you mean? I'm building and destroying dozens of venv everyday at work using tox on Python 2.7. The virtualenv command works well, no? Do you have issues with it?
Not in particular, just that 3.3+ have official support for venvs whereas virtualenv is a bit of a hack by necessity. However, the second point is the real reason I'd rather avoid venvs for this: to make sure that the interpreters actually use the same exact code, so that there can't be any setup.py shenanigans that do things differently between versions/implementations.