Specific env activation doesn't set VIRTUAL_ENV variable.

[proofit404]

Many tools need this variable install properly. For example jedi project. Also many users set their prompt with it. So it really necessary for us.

$ pyenv shell venv27-default
$ echo $VIRTUAL_ENV

$

[yyuu]

Setting VIRTUAL_ENV in pyenv is not so easy because the version in pyenv will be determined on runtime.

As an alternative approach, I added new pyenv command of pyenv activate which just activates virtualenv. Because this uses genuine activate script, it should behave as same as standard virtualenv.

$ pyenv activate venv27
$ vi foo.py

Please give activate branch a try.

[proofit404]

$ pyenv activate venv-default
pyenv: no such command `activate'

and

$ pyenv deactivate
pyenv: no such command `deactivate'

but they autocomplete work correctly...

[yyuu]

@proofit404 Please restart your shell and try again.

[proofit404]

Maybe it's necessary to add activate/deactivate to pyenv function as they starts with sh-*?

[yyuu]

It is depending the bootstrap process of pyenv (pyenv-init).

Because the pyenv function caches the list of sh- commands in its declaration (see the output from declare -f pyenv), the pyenv needs to be reloaded to add such commands. Just restarting the shell is the easiest way to take effect.

[proofit404]

Seams like a problem on my side. I reinstall pyenv from scratch and this is what I got at current point trying activate kinder-default virtual env

$ pyenv version
3.3.2 (set by /home/aamalyshev/.pyenv/version)
$ pyenv activate kinder-default
(eval):1: permission denied: /home/aamalyshev/.pyenv/versions/2.6.9
*kinder-default* $ pyenv deactivate
deactivate () {
    unset pydoc
    if [ -n "$_OLD_VIRTUAL_PATH" ]
    then
        PATH="$_OLD_VIRTUAL_PATH" 
        export PATH
        unset _OLD_VIRTUAL_PATH
    fi
    if [ -n "$_OLD_VIRTUAL_PYTHONHOME" ]
    then
        PYTHONHOME="$_OLD_VIRTUAL_PYTHONHOME" 
        export PYTHONHOME
        unset _OLD_VIRTUAL_PYTHONHOME
    fi
    if [ -n "$BASH" -o -n "$ZSH_VERSION" ]
    then
        hash -r 2> /dev/null
    fi
    if [ -n "$_OLD_VIRTUAL_PS1" ]
    then
        PS1="$_OLD_VIRTUAL_PS1" 
        export PS1
        unset _OLD_VIRTUAL_PS1
    fi
    unset VIRTUAL_ENV
    if [ ! "$1" = "nondestructive" ]
    then
        unset -f deactivate
    fi
}
$

[yyuu]

I pushed 64b2545 and f9d3984 to fix the problems. Please fetch the latest changes on activate branch.

[proofit404]

Now all works fine. My last question is about

$ pyenv activate venv26
$ deactivate
$

Is it safe to deactivate virtualenv in this way? User may just forgot it.

[proofit404]

This is what I got:

$ python --version
Python 3.3.2
$ pyenv activate venv26
*venv26* $ python --version
Python 2.6.9
*venv26* $ deactivate
$ python --version
Python 2.6.9
$ 

[yyuu]

The pyenv deactivates acts just like deactivate; pyenv shell --unset. You can also use deactivate directly. (the shell version in pyenv will persist if use deactivate instead of pyenv deactivate)

[proofit404]

As I think this is ready for production :)

[yyuu]

Thanks. I will merge this into master soon.

[proofit404]

Thank you for this cool stuff!