blocks|key|4149266|text|通常，激活一个virtualenv会给出一个名为的shell函数：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4149267|$+deactivate|code-block|syntax|javascript|4149268|这就让一切恢复正常了。|4149269|我刚刚又专门研究了virtualenvwrapper的代码，是的，它也支持deactivate作为摆脱所有virtualenvs的方式。|offset|length|style|CODE|4149270|如果您尝试离开环境，则命令取决于您的conda版本。最近的版本(如4.6)直接在shell中安装conda函数，在这种情况下，您可以运行：|4149271|conda+deactivate|4149272|较早的conda版本使用独立脚本来实现停用：|4149273|source+deactivate|4149274|entityMap^0|0|0|0|9|H|11|A|0|I|5|1C|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@$K|12|L|13|M|N]|$K|14|L|15|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@$K|17|L|18|M|N]|$K|19|L|1A|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|X|$]]

Usually, activating a virtualenv gives you a shell function named:

<pre><code>$ deactivate
</code></pre>

which puts things back to normal.

I have just looked specifically again at the code for <code>virtualenvwrapper</code>, and, yes, it too supports <code>deactivate</code> as the way to escape from all virtualenvs.

If you are trying to leave an <a href="https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)" rel="noreferrer">Anaconda</a> environment, the command depends upon your version of <code>conda</code>. Recent versions (like 4.6) install a <code>conda</code> function directly in your shell, in which case you run:

<pre><code>conda deactivate
</code></pre>

Older conda versions instead implement deactivation using a stand-alone script:

<pre><code>source deactivate
</code></pre>

blocks|key|932607|text|我在处理安装程序脚本时也遇到了同样的问题。我看了一下bin/activate_this.py做了什么，并颠倒了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|932608|示例：|932609|#!+/usr/bin/python
#+-*-+coding:+utf-8+-*-
import+os
import+sys

#+Path+to+virtualenv
venv_path+=+os.path.join('/home',+'sixdays',+'.virtualenvs',+'test32')

#+Save+old+values
old_os_path+=+os.environ['PATH']
old_sys_path+=+list(sys.path)
old_sys_prefix+=+sys.prefix


def+deactivate():
++++#+Change+back+by+setting+values+to+starting+values
++++os.environ['PATH']+=+old_os_path
++++sys.prefix+=+old_sys_prefix
++++sys.path[:0]+=+old_sys_path


#+Activate+the+virtualenvironment
activate_this+=+os.path.join(venv_path,+'bin/activate_this.py')
execfile(activate_this,+dict(__file__=activate_this))


#+Print+list+of+pip+packages+for+virtualenv+for+example+purpose
import+pip
print+str(pip.get_installed_distributions())

#+Unload+pip+module
del+pip

#+Deactivate/switch+back+to+initial+interpreter
deactivate()

#+Print+list+of+initial+environment+pip+packages+for+example+purpose
import+pip
print+str(pip.get_installed_distributions())|code-block|syntax|javascript|932610|我不能百分之百确定它是否能像预期的那样工作。我可能完全漏掉了什么。|932611|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same problem while working on an installer script. I took a look at what the bin/activate_this.py did and reversed it.

Example:

<pre><code>#! /usr/bin/python
# -*- coding: utf-8 -*-
import os
import sys

# Path to virtualenv
venv_path = os.path.join('/home', 'sixdays', '.virtualenvs', 'test32')

# Save old values
old_os_path = os.environ['PATH']
old_sys_path = list(sys.path)
old_sys_prefix = sys.prefix


def deactivate():
 # Change back by setting values to starting values
 os.environ['PATH'] = old_os_path
 sys.prefix = old_sys_prefix
 sys.path[:0] = old_sys_path


# Activate the virtualenvironment
activate_this = os.path.join(venv_path, 'bin/activate_this.py')
execfile(activate_this, dict(__file__=activate_this))


# Print list of pip packages for virtualenv for example purpose
import pip
print str(pip.get_installed_distributions())

# Unload pip module
del pip

# Deactivate/switch back to initial interpreter
deactivate()

# Print list of initial environment pip packages for example purpose
import pip
print str(pip.get_installed_distributions())
</code></pre>

I am not 100% sure if it works as intended. I may have missed something completely.

blocks|key|4149338|text|我定义了一个alias，workoff，与workon相反|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4149339|alias+workoff='deactivate'|code-block|syntax|javascript|4149340|这很容易记住：|4149341|[bobstein@host+~]$+workon+django_project
(django_project)[bobstein@host+~]$+workoff
[bobstein@host+~]$|4149342|entityMap|0|LINK|mutability|MUTABLE|url|https://askubuntu.com/questions/17536/how-do-i-create-a-permanent-bash-alias^0|C|7|L|6|6|5|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

I defined an <a href="https://askubuntu.com/questions/17536/how-do-i-create-a-permanent-bash-alias">alias</a>, workoff, as the opposite of workon:

<pre><code>alias workoff='deactivate'
</code></pre>

It is easy to remember:

<pre><code>[bobstein@host ~]$ workon django_project
(django_project)[bobstein@host ~]$ workoff
[bobstein@host ~]$
</code></pre>

blocks|key|932665|text|使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|932666|$+deactivate+|code-block|syntax|javascript|932667|如果这不起作用，请尝试|932668|$+source+deactivate|932669|任何了解Bash+source工作原理的人都会觉得这很奇怪，但一些围绕source+activate的包装器/工作流将其实现为对virtualenv的补充/对等物。您的里程可能会有所不同。|offset|length|style|CODE|932670|entityMap|0|LINK|mutability|MUTABLE|url|https://superuser.com/a/46146/3376^0|0|0|0|0|9|6|Z|F|4|B|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]|$M|15|N|16|O|P]]|9|@$M|17|N|18|1|19]]|A|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Use:

<pre><code>$ deactivate 
</code></pre>

If this doesn't work, try 

<pre><code>$ source deactivate
</code></pre>

Anyone who knows how <a href="https://superuser.com/a/46146/3376">Bash <code>source</code></a> works will think that's odd, but some wrappers/workflows around virtualenv implement it as a complement/counterpart to <code>source activate</code>. Your mileage may vary.

blocks|key|28899|text|要激活Python虚拟环境，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|28900|$cd+~/python-venv/
$./bin/activate|code-block|syntax|javascript|28901|要停用，请执行以下操作：|28902|$deactivate|28903|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

To activate a Python virtual environment:

<pre><code>$cd ~/python-venv/
$./bin/activate
</code></pre>

To deactivate:

<pre><code>$deactivate
</code></pre>

blocks|key|29793|text|您可以使用virtualenvwrapper来简化您使用virtualenv的方式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|29794|安装virtualenvwrapper|29795|pip+install+virtualenvwrapper|code-block|syntax|javascript|29796|如果您使用的是标准shell，请打开您的~/.bashrc或~/.zshrc+(如果您使用Oh+My+Zsh+)。添加这两行：|29797|export+WORKON_HOME=$HOME/.virtualenvs
source+/usr/local/bin/virtualenvwrapper.sh|29798|要激活现有的虚拟环境，请使用命令workon|29799|$+workon+myenv
(myenv)$|29800|要停用您的虚拟环境，请执行以下操作：|29801|(myenv)$+deactivate|29802|下面是my+tutorial，逐步介绍如何安装virtualenv和virtualenvwrapper。|29803|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Z_shell#Oh_My_Zsh|1|http://levipy.com/virtualenv-and-virtualenvwrapper-tutorial/^0|5|H|S|A|0|2|H|0|0|K|9|U|8|19|9|0|0|0|G|6|0|0|0|0|3|B|1|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1I|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|O|3|P|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|S|3|T|5|J|7|1V|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1W|8|@]|D|@]|E|$]]|$1|W|3|X|5|J|7|1X|8|@]|D|@]|E|$K|L]]|$1|Y|3|Z|5|6|7|1Y|8|@]|D|@$9|1Z|A|20|1|21]]|E|$]]|$1|10|3|-4|5|6|7|22|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]|18|$5|13|14|15|E|$16|19]]]]

You can use <code>virtualenvwrapper</code> in order to ease the way you work with <code>virtualenv</code>.

Installing <code>virtualenvwrapper</code>:

<pre><code>pip install virtualenvwrapper
</code></pre>

If you are using a standard shell, open your <code>~/.bashrc</code> or <code>~/.zshrc</code> if you use <a href="https://en.wikipedia.org/wiki/Z_shell#Oh_My_Zsh" rel="noreferrer">Oh My Zsh</a>. Add these two lines:

<pre><code>export WORKON_HOME=$HOME/.virtualenvs
source /usr/local/bin/virtualenvwrapper.sh
</code></pre>

To activate an existing virtualenv, use command <code>workon</code>:

<pre><code>$ workon myenv
(myenv)$
</code></pre>

In order to deactivate your virtualenv:

<pre><code>(myenv)$ deactivate
</code></pre>

Here is <a href="http://levipy.com/virtualenv-and-virtualenvwrapper-tutorial/" rel="noreferrer">my tutorial</a>, step by step on how to install virtualenv and virtualenvwrapper.

blocks|key|4149520|text|我使用的是基于autoenv的zsh-autoenv。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4149521|4149522|+zsh-autoenv自动生成(已知/白名单)+.autoenv.zsh文件，通常在项目根目录中使用。它处理“进入”和“离开”事件，嵌套和存储变量(覆盖和恢复)。|blockquote|style|CODE|4149523|4149524|4149525|下面是一个示例：|4149526|;+cd+dtree+
Switching+to+virtual+environment:+Development+tree+utiles
;dtree(feature/task24%7C✓);+cat+.autoenv.zsh+++++++
#+Autoenv.
echo+-n+"Switching+to+virtual+environment:+"
printf+"\e[38;5;93m%25s\e[0m\n"+"Development+tree+utiles"
workon+dtree
#+eof
dtree(feature/task24%7C✓);+cat+.autoenv_leave.zsh+
deactivate|code-block|syntax|javascript|4149527|因此，当我离开dtree目录时，虚拟环境会自动退出。|4149528|"Development+tree+utiles"只是一个名字…这里没有隐蔽的手段链接到光明会。|4149529|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/kennethreitz/autoenv|1|https://github.com/Tarrasch/zsh-autoenv|2^0|7|7|0|F|B|1|0|0|P|C|1|B|2|0|0|0|0|0|7|5|0|0|P|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]|$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1F|8|@$A|1G|B|1H|H|I]]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|J|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1N|8|@]|9|@]|C|$]]|$1|N|3|O|5|P|7|1O|8|@]|9|@]|C|$Q|R]]|$1|S|3|T|5|6|7|1P|8|@$A|1Q|B|1R|H|I]]|9|@]|C|$]]|$1|U|3|V|5|6|7|1S|8|@$A|1T|B|1U|H|I]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]|14|$5|Z|10|11|C|$12|15]]|16|$5|Z|10|11|C|$12|15]]]]

I use <a href="https://github.com/Tarrasch/zsh-autoenv" rel="nofollow noreferrer">zsh-autoenv</a> which is based off <a href="https://github.com/kennethreitz/autoenv" rel="nofollow noreferrer">autoenv</a>. 

<blockquote>
 <a href="https://github.com/Tarrasch/zsh-autoenv" rel="nofollow noreferrer">zsh-autoenv</a> automatically
 sources (known/whitelisted) <code>.autoenv.zsh</code> files, typically used in
 project root directories. It handles "enter" and leave" events,
 nesting, and stashing of variables (overwriting and restoring).
</blockquote>

Here is an example:

<pre><code>; cd dtree 
Switching to virtual environment: Development tree utiles
;dtree(feature/task24|✓); cat .autoenv.zsh 
# Autoenv.
echo -n "Switching to virtual environment: "
printf "\e[38;5;93m%s\e[0m\n" "Development tree utiles"
workon dtree
# eof
dtree(feature/task24|✓); cat .autoenv_leave.zsh 
deactivate
</code></pre>

So when I leave the <code>dtree</code> directory, the virtual environment is automatically exited.

<code>"Development tree utiles"</code> is just a name… No hidden mean linking to the Illuminati in here.

blocks|key|1329377|text|使用deactivate。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1329378|(my_env)+user@user:~/my_env$+deactivate
user@user-Lenovo-E40-80:~/my_env$+|code-block|syntax|javascript|1329379|注意，(my_env)已经不存在了。|1329380|entityMap^0|2|A|0|0|3|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Use <code>deactivate</code>.

<pre><code>(my_env) user@user:~/my_env$ deactivate
user@user-Lenovo-E40-80:~/my_env$ 
</code></pre>

Note, <code>(my_env)</code> is gone.

blocks|key|932894|text|我发现在Miniconda3环境中，我必须运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|932895|conda+deactivate|code-block|syntax|javascript|932896|deactivate和source+deactivate都不适合我。|offset|length|style|CODE|932897|entityMap^0|0|0|0|A|B|H|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I found that when within a Miniconda3 environment I had to run:

<pre><code>conda deactivate
</code></pre>

Neither <code>deactivate</code> nor <code>source deactivate</code> worked for me.

blocks|key|932927|text|由于通过采购~/bin/activate创建的deactivate函数不能通过在~/bin中查找这样的命令的常用方法来发现，因此您可能希望创建一个只执行函数deactivate的命令。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|932928|问题是，包含一个命令deactivate的名为deactivate的脚本，如果在不在venv中时意外执行，将导致无限循环。一个常见的错误。|932929|这可以通过仅在函数存在的情况下执行deactivate来避免(即，已经通过采购activate创建)。|932930|#!/bin/bash

declare+-Ff+deactivate++&&+deactivate|code-block|syntax|javascript|932931|entityMap^0|6|E|N|A|14|5|26|A|0|A|A|N|A|0|H|A|13|8|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|19|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|P|$]]

Since the <code>deactivate</code> function created by sourcing <code>~/bin/activate</code> cannot be discovered by the usual means of looking for such a command in <code>~/bin</code>, you may wish to create one that just executes the function <code>deactivate</code>.

The problem is that a script named <code>deactivate</code> containing a single command <code>deactivate</code> will cause an endless loop if accidentally executed while not in the venv. A common mistake.

This can be avoided by only executing <code>deactivate</code> if the function exists (i.e. has been created by sourcing <code>activate</code>).

<pre><code>#!/bin/bash

declare -Ff deactivate &amp;&amp; deactivate
</code></pre>

blocks|key|932993|text|要使用venv的deactivate+activate+脚本提供的功能，您需要相信停用函数是经过正确编码的，以便干净地将所有环境变量重置回它们以前的状态-不仅要考虑原始激活，还要考虑任何开关、配置或您在此期间可能完成的其他工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|932994|这可能是好的，但它确实引入了一个新的、非零的风险，使您的环境在事后被修改。|932995|然而，从技术上讲，进程不可能直接更改其父进程的环境变量，因此我们可以使用单独的子shell来绝对确保我们的venv不会留下任何残留的更改：|932996|932997|要激活，请执行以下操作：|932998|$+bash+--init-file+PythonVenv/bin/activate|932999|933000|这将在venv周围启动一个新的shell。您的原始bash外壳保持不变。|unordered-list-item|933001|933002|要停用，请执行以下操作：|933003|$+exit或[CTRL]%2B[D]|933004|933005|这会退出venv所在的整个shell，并返回到激活脚本对shell进行任何更改之前的原始shell|933006|933007|933008|示例：|933009|[user@computer+~]$+echo+$VIRTUAL_ENV
No+virtualenv!

[user@computer+~]$+bash+--init-file+PythonVenv/bin/activate

(PythonVenv)+[user@computer+~]$+echo+$VIRTUAL_ENV
/home/user/PythonVenv

(PythonVenv)+[user@computer+~]$+exit
exit

[user@computer+~]$+echo+$VIRTUAL_ENV
No+virtualenv!|code-block|syntax|javascript|933010|entityMap^0|8|A|J|8|S|5|8|A|J|8|0|0|M|S|1H|4|0|0|0|0|16|0|0|3|4|P|4|0|0|0|0|6|7|6|E|3|0|0|4|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|D]|$9|1L|A|1M|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1N|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|D]]|E|@]|F|$]]|$1|K|3|-4|5|6|7|1T|8|@]|E|@]|F|$]]|$1|L|3|M|5|6|7|1U|8|@]|E|@]|F|$]]|$1|N|3|O|5|6|7|1V|8|@$9|1W|A|1X|B|D]]|E|@]|F|$]]|$1|P|3|-4|5|6|7|1Y|8|@]|E|@]|F|$]]|$1|Q|3|R|5|S|7|1Z|8|@$9|20|A|21|B|D]|$9|22|A|23|B|D]]|E|@]|F|$]]|$1|T|3|-4|5|6|7|24|8|@]|E|@]|F|$]]|$1|U|3|V|5|6|7|25|8|@]|E|@]|F|$]]|$1|W|3|X|5|6|7|26|8|@$9|27|A|28|B|D]|$9|29|A|2A|B|D]|$9|2B|A|2C|B|D]]|E|@]|F|$]]|$1|Y|3|-4|5|6|7|2D|8|@]|E|@]|F|$]]|$1|Z|3|10|5|S|7|2E|8|@$9|2F|A|2G|B|D]]|E|@]|F|$]]|$1|11|3|-4|5|6|7|2H|8|@]|E|@]|F|$]]|$1|12|3|-4|5|6|7|2I|8|@]|E|@]|F|$]]|$1|13|3|14|5|6|7|2J|8|@]|E|@]|F|$]]|$1|15|3|16|5|17|7|2K|8|@]|E|@]|F|$18|19]]|$1|1A|3|-4|5|6|7|2L|8|@]|E|@]|F|$]]]|1B|$]]

Using the <code>deactivate</code> feature provided by the venv's <code>activate</code> script requires you to trust the deactivation function to be properly coded to cleanly reset all environment variables back to how they were before— taking into account not only the original activation, but also any switches, configuration, or other work you may have done in the meantime.

It's probably fine, but it does introduce a new, non-zero risk of leaving your environment modified afterwards.

However, it's not technically possible for a process to directly alter the environment variables of its parent, so we can use a separate sub-shell to be absolutely sure our <code>venv</code>s don't leave any residual changes behind:

<hr>

<h2>To activate:</h2>

<code>$ bash --init-file PythonVenv/bin/activate</code>

<ul>
<li>This starts a new shell around the <code>venv</code>. Your original <code>bash</code> shell remains unmodified.</li>
</ul>

<h2>To deactivate:</h2>

<code>$ exit</code> OR <code>[CTRL]</code>+<code>[D]</code>

<ul>
<li>This exits the entire shell the <code>venv</code> is in, and drops you back to the original shell from before the activation script made any changes to the environment.</li>
</ul>

<hr>

<h2>Example:</h2>

<pre><code>[user@computer ~]$ echo $VIRTUAL_ENV
No virtualenv!

[user@computer ~]$ bash --init-file PythonVenv/bin/activate

(PythonVenv) [user@computer ~]$ echo $VIRTUAL_ENV
/home/user/PythonVenv

(PythonVenv) [user@computer ~]$ exit
exit

[user@computer ~]$ echo $VIRTUAL_ENV
No virtualenv!
</code></pre>

blocks|key|1331851|text|对于我的特定情况，我转到工作目录|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1331852|CD+/myworkingdirectory|code-block|syntax|javascript|1331853|然后我像这样激活我的env：|1331854|my-env/scripts/activate|1331855|从这个相同的工作文件夹(/myworkingdirectory)去停用，我试着这样做，但它没有任何作用：|offset|length|style|CODE|1331856|my-env/scripts/deactivate|1331857|这是可行的：|1331858|deactivate|1331859|entityMap^0|0|0|0|0|C|J|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

For my particular case, I go to to the working directory
<pre><code>CD /myworkingdirectory
</code></pre>
Then I activate my env like this:
<pre><code>my-env/scripts/activate
</code></pre>
From this same working folder (<code>/myworkingdirectory</code>) to deactivate, I tried this but it does nothing:
<pre><code>my-env/scripts/deactivate
</code></pre>
This does work:
<pre><code>deactivate
</code></pre>

blocks|key|29941|text|要激活Python虚拟环境，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29942|source+venv/bin/activate|code-block|syntax|javascript|29943|注意:这里的"venv“是你的virtualenvironment文件夹名|offset|length|style|CODE|29944|要停用，请执行以下操作：|29945|deactivate|29946|或|29947|source+deactivate|29948|entityMap^0|0|0|F|I|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

To activate a Python virtual environment:
<pre><code>source venv/bin/activate
</code></pre>
Note: Here &quot;venv&quot; is your <code>virtualenvironment</code> folder name
To deactivate :
<pre><code>deactivate
</code></pre>
or
<pre><code>source deactivate
</code></pre>

blocks|key|4149775|text|运行deactivate+[name+of+your+environment]能够从您的python环境中退出/停用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4149776|python3.6+Windows+10的示例：|4149777|PS+C:\Users\kyrlon\Desktop>+py+-m+venv+env1
PS+C:\Users\kyrlon\Desktop>+.\env1\Scripts\activate
(env1)+PS+C:\Users\kyrlon\Desktop>+deactivate+env1
PS+C:\Users\klongwood3\Desktop>+py+-m+venv+env1|code-block|syntax|javascript|4149778|Linux+Ubuntu+20.04+LTS+Desktop上的python3.9示例：|4149779|kyrlon@pc1:~$+python3+-m+venv+venv1
kyrlon@pc1:~$+source+venv1/bin/activate
(venv1)+kyrlon@pc1:~$+deactivate+venv1
kyrlon@pc1:~$|4149780|entityMap^0|2|11|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Running <code>deactivate [name of your environment]</code> is able to exit/deactivate from your python environment.
Example with python3.6 Windows 10:
<pre><code>PS C:\Users\kyrlon\Desktop&gt; py -m venv env1
PS C:\Users\kyrlon\Desktop&gt; .\env1\Scripts\activate
(env1) PS C:\Users\kyrlon\Desktop&gt; deactivate env1
PS C:\Users\klongwood3\Desktop&gt; py -m venv env1
</code></pre>
Example with python3.9 on Linux Ubuntu 20.04 LTS Desktop:
<pre><code>kyrlon@pc1:~$ python3 -m venv venv1
kyrlon@pc1:~$ source venv1/bin/activate
(venv1) kyrlon@pc1:~$ deactivate venv1
kyrlon@pc1:~$
</code></pre>

blocks|key|1329533|text|如果有人想知道如何在deactivate或source+deactivate不起作用的情况下将其停用，请键入：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1329534|deactivate+<virtual+environment+name>|1329535|对我来说就像一个护身符！|1329536|entityMap^0|A|A|L|H|0|0|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

if anyone is trying to figure out how to deactivate it if <code>deactivate</code> or <code>source deactivate</code> does not work then type:
<code>deactivate &lt;virtual environment name&gt;</code>
worked like a charm for me!

blocks|key|4149827|text|在我的例子中，我能够使用env-name\scripts\activate激活虚拟环境，并使用deactivate将其停用。然而，在我的windows+PC上运行更新后，deactivate不再被识别为内部或外部命令。从那一刻起，我使用的是env-name\scripts\deactivate，这解决了问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4149828|entityMap^0|C|P|1B|A|2D|A|3C|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I my case, I was able to activate virtual environment using <code>env-name\scripts\activate</code> and deactivate it using <code>deactivate</code>. However, after running update on my windows PC <code>deactivate</code> was no longer recognized as an internal or external command. What I used from that moment onward is <code>env-name\scripts\deactivate</code> and that solved the problem.

I'm using virtualenv and the virtualenvwrapper. I can switch between virtualenv's just fine using the <code>workon</code> command.
<pre><code>me@mymachine:~$ workon env1
(env1)me@mymachine:~$ workon env2
(env2)me@mymachine:~$ workon env1
(env1)me@mymachine:~$ 
</code></pre>
How do I exit all virtual environments and work on my system environment again? Right now, the only way I have of getting back to <code>me@mymachine:~$</code> is to exit the shell and start a new one. That's kind of annoying. Is there a command to work on &quot;nothing&quot;, and if so, what is it? If such a command does not exist, how would I go about creating it?

How to leave/exit/deactivate a Python virtualenv

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我使用的是virtualenv和virtualenvwrapper。我可以使用workon命令在virtualenv之间切换。me@mymachine:~$ workon env1(env1)me@mymachine:~$ workon env2(env2)me@mymachine:~$ workon env1(env...

问如何退出/退出/停用Python虚拟环境
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何退出/退出/停用Python虚拟环境EN