virtualenv lookup fail - 1.7.1 regression on Windows

[pytoxbot]

• Bitbucket: https://bitbucket.org/hpk42/tox/issue/158
• Originally reported by: @techtonik
• Originally created at: 2014-03-15T10:26:12.528

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.

[pytoxbot]

Original comment by @techtonik

Any chance to see a new release soon? =)

[pytoxbot]

Original comment by @hpk42

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.

→ <>

[pytoxbot]

Original comment by @ionelmc

Fix in pull request #89

[pytoxbot]

Original comment by @techtonik

I confirm that #155 is the same issue.

[pytoxbot]

Original comment by @cjw296

I think #155 is the same issue, or at the very least related. It's been broken for around 2 months now.

[pytoxbot]

Original comment by @techtonik

python -m tox

[pytoxbot]

Original comment by @ionelmc

I have assumed that you have the correct path in #84, even on windows. How would you run tox otherwise ?!