From 5033c3ba0d29c052214a9d1a5b5d698997b16a49 Mon Sep 17 00:00:00 2001 From: Yamashita Yuu Date: Mon, 3 Feb 2014 16:13:41 +0900 Subject: [PATCH] Update README about `pyenv activate --unset` (#15) --- README.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c3d6ad0..d957d93 100644 --- a/README.md +++ b/README.md @@ -89,14 +89,28 @@ Some external tools (e.g. [jedi](https://github.com/davidhalter/jedi)) might req $ pyenv activate venv27 `pyenv activate` acts almost like following commands. +The activate'd virtualenv will be persisted as _shell_ version. $ pyenv shell venv27 $ source "$(pyenv prefix venv27)/bin/activate" -You can deactivate the activate'd virtualenv by `pyenv deactivate`. +### Deactivate virtualenv + +You can `deactivate` the activate'd virtualenv by `pyenv deactivate`. $ pyenv deactivate +Or, there is an alias in `activate` command. +This is prepared for similality between other `pyenv` commands like `shell` and `local`. + + $ pyenv activate --unset + +`pyenv deactivate` acts almost like following commands. +You can also use virtualenv's `deactivate` in place of `pyenv deactivate`, +but be careful with the _shell_ version because it will be persisted even if `deactivate` has invoked. + + $ deactivate + $ pyenv shell --unset ### Special environment variables