Implicitly add WORKON_HOME to python.venvFolders

[DonJayamanne]

From @zgoda on May 19, 2017 11:30

I work almost exclusively in virtualenvs and I'd like to be able to select interpreter from list of virtualenvs if both workon command and WORKON_HOME envvar exist.

workon is shell command installed by virtualenvwrapper. When invoked without argument it lists available virtualenvs under its control, in alphabetical order:

$ workon
bde
brewlog
cocos
...
tsp
twt
wsm
yg01

Now I have to set complete path to interpreter in form of $WORKON_HOME/<envname>/bin/python. An alternative is to get virtualenvs by listing subdirs of $WORKON_HOME (this is exactly what workon does).

Copied from original issue: DonJayamanne/pythonVSCode#968

[brettcannon]

This would also help with pipenv who reads from WORKON_HOME as an alternative location to place virtual environments.

[kweerious]

Looking over the discussion from #2106 and messing around with virtualenvwrapper created environments I found that if you run with the default setup virtualenvwrapper also drops its hook files in that directory. If removed then venvPath works properly.

Might I suggest only acting on directories found within venvPath options?

For anyone using virtualenvwrapper wanting a workaround for now, use the VIRTUALENVWRAPPER_HOOK_DIR to set some different directory and remove your non-environments from your .virtualenvs

Example

export VIRTUALENVWRAPPER_HOOK_DIR=$HOME/.virtualenv_hooks
source /usr/local/bin/virtualenvwrapper.sh
export WORKON_HOME=$HOME/.virtualenvs

"python.venvPath": "/Users/$USER/.virtualenvs"

[kimadeline]

Todo:

• Add WORKON_HOME to defaults if set
• Update docstring in package.json to say that we support pipenv and virtualenvwrapper directories (check settings UI) 🎉