Document how to define/override the virtualenv path

Issue #195 on hold
Eric Higgins created an issue

Virtualenv supports custom bootstrap scripts which extend the virtualenv library and replaces

$ virtualenv ENV

with

$ ./virtualenv.boostrap.py ENV

The documentation for tox does not make it clear how to override the path to virtualenv, which would allow these bootstrap scripts to be called instead.

Additional reading:

Comments (5)

  1. Holger Krekel repo owner

    I don't think you can change the virtualenv path currently. If this is a per-project (and thus per tox.ini) specific setting, a PR could introduce a new "virtualenv_path" config variable in the [tox] section, i guess. I am happy to review such a PR.

  2. Eric Higgins reporter

    Ok, thanks for the update. I'd be happy to provide such a PR, but I could use some guidance on where you think that should be implemented. There's already a path property defined for tox/_venv.py:VirtualEnv.path, which could get confusing when it comes to naming (I thought that's what it was storing, but I guess not).

  3. Holger Krekel repo owner

    something like venv_create_path would make sense as an attribute. VirtualEnv.path is the path to the (to-be-created) virtualenv directory, not the path to how to create a virtualenv.

  4. Log in to comment