virtualenv lookup fail - 1.7.1 regression on Windows

Issue #158 on hold
anatoly techtonik created an issue

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.

Comments (9)

  1. Ionel Cristian Mărieș

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

  2. Holger Krekel repo owner

    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.

    → <<cset a813c18ba50a>>

  3. Log in to comment