Pull request #84 broke tox for Windows, because virtualenv is not added into %PATH%. Looking up for virtualenv through interpreter is a way to go. At least this way should have been left as a fallback.
Ionel Cristian Mărieș
I have assumed that you have the correct path in #84, even on windows. How would you run tox otherwise ?!
python -m tox
I think #155 is the same issue, or at the very least related. It's been broken for around 2 months now.
fix issue158 and fix issue155: windows/virtualenv properly works now:
call virtualenv through "python -m virtualenv" with the same
interpreter which invoked tox. Thanks Chris Withers, Ionel Maries Cristian.