m/pyenv-virtualenv
1
0
Fork 0
mirror of https://github.com/pyenv/pyenv-virtualenv.git synced 2025-11-13 14:03:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README about pyenv activate --unset (#15)

Browse Source
This commit is contained in:
Yamashita Yuu
2014-02-03 16:13:41 +09:00
parent a958640776
commit 5033c3ba0d
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -89,14 +89,28 @@ Some external tools (e.g. [jedi](https://github.com/davidhalter/jedi)) might req
$ pyenv activate venv27 $ pyenv activate venv27
`pyenv activate` acts almost like following commands. `pyenv activate` acts almost like following commands.
The activate'd virtualenv will be persisted as _shell_ version.
$ pyenv shell venv27 $ pyenv shell venv27
$ source "$(pyenv prefix venv27)/bin/activate" $ 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 $ 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 ### Special environment variables