blocks|key|1970050|text|子进程环境在它不复存在的那一刻就丢失了，并且将环境内容从那里移动到父进程是有点棘手的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1970051|您可能需要生成一个shell脚本(您可以动态生成一个脚本到/tmp)，该脚本将把virtualenv环境变量输出到一个文件，然后在父Python进程中读取该文件并将其放入os.environ中。|1970052|或者，您可以简单地解析用于打开(“bin/+activate”)中的行的激活脚本，手动提取内容，然后放入os.environ。这很棘手，但也不是不可能。|1970053|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The child process environment is lost in the moment it ceases to exist, and moving the environment content from there to the parent is somewhat tricky.

You probably need to spawn a shell script (you can generate one dynamically to /tmp) which will output the virtualenv environment variables to a file, which you then read in the parent Python process and put in os.environ.

Or you simply parse the activate script in using for the line in open("bin/activate"), manually extract stuff, and put in os.environ. It is tricky, but not impossible.

blocks|key|1756509|text|事实证明，是的，问题并不简单，但解决方案却很简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1756510|首先，我必须创建一个shell脚本来包装"source“命令。也就是说，我使用了“。相反，因为我读到过Bash脚本使用它比源代码更好。|1756511|#!/bin/bash
.+/path/to/env/bin/activate|code-block|syntax|javascript|1756512|然后，从我的Python脚本中，我可以简单地执行以下操作：|1756513|import+os
os.system('/bin/bash+--rcfile+/path/to/myscript.sh')|1756514|整个技巧在于--rcfile参数。|offset|length|style|CODE|1756515|当Python解释器退出时，它将当前shell留在激活的环境中。|1756516|赢!|1756517|entityMap^0|0|0|0|0|0|6|8|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@$O|14|P|15|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

It turns out that, yes, the problem is not simple, but the solution is.

First I had to create a shell script to wrap the "source" command. That said I used the "." instead, because I've read that it's better to use it than source for Bash scripts.

<pre><code>#!/bin/bash
. /path/to/env/bin/activate
</code></pre>

Then from my Python script I can simply do this:

<pre><code>import os
os.system('/bin/bash --rcfile /path/to/myscript.sh')
</code></pre>

The whole trick lies within the <code>--rcfile</code> argument.

When the Python interpreter exits it leaves the current shell in the activated environment.

Win!

blocks|key|1970263|text|如果您想要在virtualenv下运行Python子进程，可以通过使用virtualenv的/bin/目录中的Python解释器运行脚本来实现：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1970264|import+subprocess

#+Path+to+a+Python+interpreter+that+runs+any+Python+script
#+under+the+virtualenv+/path/to/virtualenv/
python_bin+=+"/path/to/virtualenv/bin/python"

#+Path+to+the+script+that+must+run+under+the+virtualenv
script_file+=+"must/run/under/virtualenv/script.py"

subprocess.Popen([python_bin,+script_file])|code-block|syntax|javascript|1970265|但是，如果您希望在当前Python解释器下而不是在子进程下激活virtualenv，则可以使用activate_this.py脚本：|offset|length|style|CODE|1970266|#+Doing+execfile()+on+this+file+will+alter+the+current+interpreter's
#+environment+so+you+can+import+libraries+in+the+virtualenv
activate_this_file+=+"/path/to/virtualenv/bin/activate_this.py"

execfile(activate_this_file,+dict(__file__=activate_this_file))|1970267|entityMap^0|0|0|1B|G|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If you want to run a Python subprocess under the virtualenv, you can do that by running the script using the Python interpreter that lives inside virtualenv's /bin/ directory:
<pre><code>import subprocess

# Path to a Python interpreter that runs any Python script
# under the virtualenv /path/to/virtualenv/
python_bin = &quot;/path/to/virtualenv/bin/python&quot;

# Path to the script that must run under the virtualenv
script_file = &quot;must/run/under/virtualenv/script.py&quot;

subprocess.Popen([python_bin, script_file])
</code></pre>
However, if you want to activate the virtualenv under the current Python interpreter instead of a subprocess, you can use the <code>activate_this.py</code> script:
<pre><code># Doing execfile() on this file will alter the current interpreter's
# environment so you can import libraries in the virtualenv
activate_this_file = &quot;/path/to/virtualenv/bin/activate_this.py&quot;

execfile(activate_this_file, dict(__file__=activate_this_file))
</code></pre>

blocks|key|1970408|text|要根据官方Virtualenv+documentation运行另一个Python环境，您可以在命令行中指定可执行Python二进制文件的完整路径，只需指定(之前不需要激活virtualenv+)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1970409|/path/to/virtualenv/bin/python|code-block|syntax|javascript|1970410|如果您想通过您的virtualenv从命令行调用脚本，这一点同样适用。您不需要在此之前激活它：|1970411|me$+/path/to/virtualenv/bin/python+myscript.py|1970412|对于Windows环境也是如此(无论是从命令行还是从脚本)：|1970413|>+\path\to\env\Scripts\python.exe+myscript.py|1970414|entityMap|0|LINK|mutability|MUTABLE|url|https://virtualenv.pypa.io/en/16.7.9/userguide.html#activate-script^0|5|O|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|C|$G|H]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

To run another Python environment according to the official <a href="https://virtualenv.pypa.io/en/16.7.9/userguide.html#activate-script" rel="noreferrer">Virtualenv documentation</a>, in the command line you can specify the full path to the executable Python binary, just that (no need to active the virtualenv before):
<pre><code>/path/to/virtualenv/bin/python
</code></pre>
The same applies if you want to invoke a script from the command line with your virtualenv. You don't need to activate it before:
<pre><code>me$ /path/to/virtualenv/bin/python myscript.py
</code></pre>
The same for a Windows environment (whether it is from the command line or from a script):
<pre><code>&gt; \path\to\env\Scripts\python.exe myscript.py
</code></pre>

blocks|key|1756940|text|在virtualenv的解释器下运行脚本的最简单的解决方案是将默认的shebang行替换为您的virtualenv的解释器的路径，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1756941|#!/path/to/project/venv/bin/python|code-block|syntax|javascript|1756942|使脚本可执行：|1756943|chmod+u%2Bx+script.py|1756944|运行脚本：|1756945|./script.py|1756946|瞧！|1756947|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

The simplest solution to run your script under virtualenv's interpreter is to replace the default shebang line with path to your virtualenv's interpreter like so at the beginning of the script:

<pre><code>#!/path/to/project/venv/bin/python
</code></pre>

Make the script executable: 

<pre><code>chmod u+x script.py
</code></pre>

Run the script:

<pre><code>./script.py
</code></pre>

Voila!

blocks|key|1970614|text|您应该在一个文件夹中创建所有的virtualenv，例如virt。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1970615|假设您的virtualenv文件夹名为virt，如果不是，请更改它|1970616|cd
mkdir+custom|code-block|syntax|javascript|1970617|复制以下行...|1970618|#!/usr/bin/env+bash
ENV_PATH="$HOME/virt/$1/bin/activate"
bash+--rcfile+$ENV_PATH+-i|1970619|创建一个shell脚本文件并粘贴上面的代码行...|1970620|touch+custom/vhelper
nano+custom/vhelper|1970621|授予对您的文件的可执行权限：|1970622|sudo+chmod+%2Bx+custom/vhelper|1970623|现在导出该自定义文件夹路径，以便您可以通过单击tab...在命令行上找到它。|1970624|导出自定义：“$HOME/PATH=$PATH”|1970625|现在你只需输入下面的命令就可以在任何地方使用它了…|1970626|vhelper+YOUR_VIRTUAL_ENV_FOLDER_NAME|1970627|假设它是abc，那么.|1970628|vhelper+abc|1970629|entityMap^0|F|A|S|4|0|0|0|0|0|0|0|0|0|0|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]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1H|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1I|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1J|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1K|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1L|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1M|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1N|8|@]|D|@]|E|$]]|$1|W|3|X|5|J|7|1O|8|@]|D|@]|E|$K|L]]|$1|Y|3|Z|5|6|7|1P|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|1R|8|@]|D|@]|E|$]]|$1|14|3|15|5|J|7|1S|8|@]|D|@]|E|$K|L]]|$1|16|3|17|5|6|7|1T|8|@]|D|@]|E|$]]|$1|18|3|19|5|J|7|1U|8|@]|D|@]|E|$K|L]]|$1|1A|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|1B|$]]

You should create all your <code>virtualenv</code>s in one folder, such as <code>virt</code>.

Assuming your virtualenv folder name is virt, if not change it

<pre><code>cd
mkdir custom
</code></pre>

Copy the below lines...

<pre><code>#!/usr/bin/env bash
ENV_PATH="$HOME/virt/$1/bin/activate"
bash --rcfile $ENV_PATH -i
</code></pre>

Create a shell script file and paste the above lines...

<pre><code>touch custom/vhelper
nano custom/vhelper
</code></pre>

Grant executable permission to your file:

<pre><code>sudo chmod +x custom/vhelper
</code></pre>

Now export that custom folder path so that you can find it on the command-line by clicking tab...

export PATH=$PATH:"$HOME/custom"

Now you can use it from anywhere by just typing the below command...

<pre><code>vhelper YOUR_VIRTUAL_ENV_FOLDER_NAME
</code></pre>

Suppose it is abc then...

<pre><code>vhelper abc
</code></pre>

blocks|key|1970708|text|最高答案仅适用于Python+2.x版|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1970709|对于Python+3.x，请使用以下命令：|1970710|activate_this_file+=+"/path/to/virtualenv/bin/activate_this.py"

exec(compile(open(activate_this_file,+"rb").read(),+activate_this_file,+'exec'),+dict(__file__=activate_this_file))|code-block|syntax|javascript|1970711|参考：|1970712|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|$]]

The top answer only works for Python&nbsp;2.x

For Python 3.x, use this:

<pre><code>activate_this_file = "/path/to/virtualenv/bin/activate_this.py"

exec(compile(open(activate_this_file, "rb").read(), activate_this_file, 'exec'), dict(__file__=activate_this_file))
</code></pre>

Reference: <a href="https://stackoverflow.com/questions/436198/what-is-an-alternative-to-execfile-in-python-3">What is an alternative to execfile in Python 3?</a>

blocks|key|1757121|text|对于python2/3，使用下面的代码片段，我们可以激活虚拟环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1757122|activate_this+=+"/home/<--path-->/<--virtual+env+name+-->/bin/activate_this.py"+#for+ubuntu
activate_this+=+"D:\<--+path+-->\<--virtual+env+name+-->\Scripts\\activate_this.py"+#for+windows
with+open(activate_this)+as+f:
++++code+=+compile(f.read(),+activate_this,+'exec')
++++exec(code,+dict(__file__=activate_this))|code-block|syntax|javascript|1757123|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For python2/3, Using below code snippet we can activate virtual env.
<pre><code>activate_this = &quot;/home/&lt;--path--&gt;/&lt;--virtual env name --&gt;/bin/activate_this.py&quot; #for ubuntu
activate_this = &quot;D:\&lt;-- path --&gt;\&lt;--virtual env name --&gt;\Scripts\\activate_this.py&quot; #for windows
with open(activate_this) as f:
 code = compile(f.read(), activate_this, 'exec')
 exec(code, dict(__file__=activate_this))
</code></pre>

blocks|key|1757131|text|我也遇到了同样的问题，并且在我的环境的Scripts目录中没有activate_this.py。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1757132|activate_this.py|1757133|"""By+using+execfile(this_file,+dict(__file__=this_file))+you+will
activate+this+virtualenv+environment.
This+can+be+used+when+you+must+use+an+existing+Python+interpreter,+not
the+virtualenv+bin/python
"""

try:
++++__file__
except+NameError:
++++raise+AssertionError(
++++++++"You+must+run+this+like+execfile('path/to/active_this.py',+dict(__file__='path/to/activate_this.py'))")
import+sys
import+os

base+=+os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
if(sys.platform=='win32'):
+++++site_packages+=+os.path.join(base,+'Lib',+'site-packages')
else:
+++++site_packages+=+os.path.join(base,+'lib',+'python%25s'+%25+sys.version[:3],+'site-packages')
prev_sys_path+=+list(sys.path)
import+site
site.addsitedir(site_packages)
sys.real_prefix+=+sys.prefix
sys.prefix+=+base
#+Move+the+added+items+to+the+front+of+the+path:
new_sys_path+=+[]
for+item+in+list(sys.path):
++++if+item+not+in+prev_sys_path:
++++++++new_sys_path.append(item)
++++++++sys.path.remove(item)
sys.path[:0]+=+new_sys_path|code-block|syntax|javascript|1757134|将该文件复制到您环境的Scripts目录中，并按如下方式使用它：|1757135|def+activate_virtual_environment(environment_root):
++++"""Configures+the+virtual+environment+starting+at+``environment_root``."""
++++activate_script+=+os.path.join(
++++++++environment_root,+'Scripts',+'activate_this.py')
++++execfile(activate_script,+{'__file__':+activate_script})

activate_virtual_environment('path/to/your/venv')|1757136|参考：https://github.com/dcreager/virtualenv/blob/master/virtualenv_support/activate_this.py|1757137|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dcreager/virtualenv/blob/master/virtualenv_support/activate_this.py^0|J|7|V|G|0|0|0|B|7|0|0|3|2E|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|S|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

I had the same issue and there was no <code>activate_this.py</code> in the <code>Scripts</code> directory of my environment.
activate_this.py
<pre class="lang-py prettyprint-override"><code>&quot;&quot;&quot;By using execfile(this_file, dict(__file__=this_file)) you will
activate this virtualenv environment.
This can be used when you must use an existing Python interpreter, not
the virtualenv bin/python
&quot;&quot;&quot;

try:
 __file__
except NameError:
 raise AssertionError(
 &quot;You must run this like execfile('path/to/active_this.py', dict(__file__='path/to/activate_this.py'))&quot;)
import sys
import os

base = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
if(sys.platform=='win32'):
 site_packages = os.path.join(base, 'Lib', 'site-packages')
else:
 site_packages = os.path.join(base, 'lib', 'python%s' % sys.version[:3], 'site-packages')
prev_sys_path = list(sys.path)
import site
site.addsitedir(site_packages)
sys.real_prefix = sys.prefix
sys.prefix = base
# Move the added items to the front of the path:
new_sys_path = []
for item in list(sys.path):
 if item not in prev_sys_path:
 new_sys_path.append(item)
 sys.path.remove(item)
sys.path[:0] = new_sys_path
</code></pre>
Copy the file to the <code>Scripts</code> directory of your environment and use it like this:
<pre class="lang-py prettyprint-override"><code>def activate_virtual_environment(environment_root):
 &quot;&quot;&quot;Configures the virtual environment starting at ``environment_root``.&quot;&quot;&quot;
 activate_script = os.path.join(
 environment_root, 'Scripts', 'activate_this.py')
 execfile(activate_script, {'__file__': activate_script})

activate_virtual_environment('path/to/your/venv')
</code></pre>
Refrence: <a href="https://github.com/dcreager/virtualenv/blob/master/virtualenv_support/activate_this.py" rel="nofollow noreferrer">https://github.com/dcreager/virtualenv/blob/master/virtualenv_support/activate_this.py</a>

I want to activate a virtualenv instance from a Python script.

I know it's quite easy to do, but all the examples I've seen use it to run commands within the env and then close the subprocess.

I simply want to activate the virtualenv and return to the shell, the same way that bin/activate does.

Something like this:

<pre><code>$me: my-script.py -d env-name
$(env-name)me:
</code></pre>

Is this possible?

Relevant:

<a href="http://groups.google.com/group/python-virtualenv/browse_thread/thread/15f8a9b0506abeae" rel="noreferrer">virtualenv › Invoking an env from a script</a>

Activate a virtualenv with a Python script

解释器

Windows

Python

我想从Python脚本激活一个virtualenv实例。我知道这很容易做到，但我见过的所有示例都使用它在env中运行命令，然后关闭该子进程。我只想激活virtualenv并返回到shell，就像bin/activate一样。如下所示：$me: my-script.py -d env-name$(env-name)me:...

问使用Python脚本激活virtualenv
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Python脚本激活virtualenvEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Python脚本激活virtualenv
EN