Daniel Hahler 86046fd4e8 Do not allow whitespace in VIRTUALENV_NAME ... While this could work in general, it fails in the end, because whitespace is not allowed/supported in the shebang line with the scripts in the created virtualenv.		2014-09-03 23:28:46 +02:00
..
pyenv-activate	Fix completion of pyenv activate (fixes #15)	2014-02-03 14:49:47 +09:00
pyenv-deactivate	Display error if pyenv activate was invoked as a command	2014-01-25 19:14:58 +09:00
pyenv-sh-activate	Use . instead of source to support POSIX sh	2014-08-13 10:54:18 +09:00
pyenv-sh-deactivate	Deactivate virtualenv even if it has been activated manually	2014-07-11 20:24:58 +09:00
pyenv-virtualenv	Do not allow whitespace in VIRTUALENV_NAME	2014-09-03 23:28:46 +02:00
pyenv-virtualenv-init	Indent to 2 spaces.	2014-08-13 19:51:22 +01:00
pyenv-virtualenv-prefix	Fix virtualenv-prefix when the version is system	2014-07-04 22:44:08 +09:00
pyenv-virtualenvs	remove redundant checks for pyenv-prefix	2013-06-21 19:42:46 +09:00