Issues

Issue #80 resolved

launch virtualenv using VIRTUALENVWRAPPER_PYTHON

Jan Dittberner avatarJan Dittberner created an issue

it would be great if mkvirtualenv would launch virtualenv using $VIRTUALENVWRAPPER_PYTHON like this

{{{ (cd "$WORKON_HOME" && "$VIRTUALENVWRAPPER_PYTHON" -m virtualenv "$@" && [ -d "$WORKON_HOME/$envname" ] && virtualenvwrapper_run_hook "pre_mkvirtualenv" "$envname" ) }}}

instead of running the virtualenv script from $PATH, this helps when you want to create virtualenvs for different python versions all installed to some common path (i.e. /usr/local/bin/python2.{4,5,6,7}). I use this in a Jenkins CI installation.

Comments (2)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.