Is there a way to set environment variables for each version?

[RobRoseKnows]

I'd like to be able to set environment variables specific to each virtualenv created by pyenv when I enter a directory. I found Issue #55 that seems to mention this and says it's not currently supported, but it's also from 2014, so I was wondering if anything has changed since then.

I tried adding export statements to ~/.pyenv/versions/3.6.5/envs/my-env/bin/activate (where my-env is a local 3.6.5 virtualenv set in the .python-version file) but they didn't get set. I'm planning on trying direnv as suggested in issue #55, but I was wondering if pyenv now has native support for this, or if such support is planned in the future.

[bossjones]

Came across this post in another git issue earlier today ... it has some code that is specific to miniconda, but it seems it could work in any situation. pyenv.d hook scripts: #178 (comment) ( Hope that helps @RobRoseKnows ) !

[native-api]

Pyenv-Virtualenv doesn't actually source the activate/deactivate scripts (but it does source scripts from conda activate.d/deactivate.d and profile.d).

It's possible to execute arbitrary code with an after_activate hook:

$PYENV_ROOT/plugins/<your_plugin_name>/etc/pyenv.d/activate/<your_hook_name.sh>:

your_fn_name() {
  if [[ $venv == "foo" ]]; then
    export magic_word="xyzzy"
  fi
}

after_activate your_fn_name

This script will be sourced at

pyenv-virtualenv/bin/pyenv-sh-activate

Line 47 in e8c8fd9

for script in "${scripts[@]}"; do source "$script"; done

and the hook evald at

pyenv-virtualenv/bin/pyenv-sh-activate

Line 305 in e8c8fd9

for hook in "${after_hooks[@]}"; do eval "$hook"; done

.

[skerain]

@native-api Sorry, but this is not working. After a git pull, I placed a script in the directory .pyenv/plugins/pyenv-virtualenv/etc/pyenv.d/activate/after_configure_pypi.bash. The content of my script is as follows:

configure_pypi() {
  export SOMETHING="its-a-thing"
}
after_activate configure_pypi

When I replace the last line with the direct execution of the function, a source after_configure_pypi.bash works (SOMETHING is correctly created).

When I activate my virtual environment, no SOMETHING in my environment variables.

What did I not understand ?

[native-api]

Sorry. I was writing from memory. The example above would work if activate was a regular subcommand. But it's an in-shell subcommand (implemented in pyenv-sh-activate and run by the pyenv shell function; there is also a regular activate subcommand but all it does is print an error message) -- because it needs to make changes to the active shell.

In-shell subcommands (and their hooks) need to print commands to execute in the user's shell rather than execute them directly.

I've tested the following code to work:

~/.pyenv/plugins/venv-envvars/etc/pyenv.d/activate/set-envvars.bash:

set_venv_envvars() {
    echo 'export magic_word="xyzzy"'
}

after_activate set_venv_envvars

Now:

$ pyenv activate test
(test) $ set | grep magic
magic_word=xyzzy

Note that you'll probably also need a similar deactivate hook to unset any of the envvars you set -- otherwise, they'd stick after deactivation which you probably don't want.

[skerain]

Thank you for taking the time to respond to me, it works.