blocks|key|746268|text|在没有空格的路径中创建您的virtualenv环境。这就是为什么它会发生：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|746269|当您创建环境时，它会设置一个bin目录。在bin目录中是与环境相关所有可执行文件。有些是脚本。正如您可能知道的，hashbang用于告诉系统使用哪个解释器来运行脚本。您可能经常在脚本的顶部看到以下内容：|offset|length|style|CODE|746270|#!/usr/bin/env+python|code-block|syntax|javascript|746271|如果脚本位于/tmp/test.py，则通知系统运行此命令来执行脚本：|746272|/usr/bin/env+python+/tmp/test.py|746273|在您的示例中，virtualenv创建的脚本如下所示：|746274|#!/tmp/oh+no/bin/python|746275|当系统尝试执行该命令时，它将尝试执行带有参数no/bin/python和/tmp/test.py的命令/tmp/oh。/tmp/oh不存在，因此失败。|746276|entityMap^0|0|E|3|L|3|0|0|6|C|0|0|0|0|M|D|10|C|1F|7|1N|7|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]|$D|1G|E|1H|F|G]|$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|X|$]]

Create your virtualenv environment within a path without spaces. This is why it is happening:

When you create an environment, it sets up a <code>bin</code> directory. In that <code>bin</code> directory are all the executables relating to the environment. Some are scripts. As you may know, hashbangs are used to tell the system what interpreter to use to run the script. You may see this at the top of scripts often:

<pre><code>#!/usr/bin/env python
</code></pre>

If the script is at <code>/tmp/test.py</code>, that tells the system to run this command to execute the script:

<pre><code>/usr/bin/env python /tmp/test.py
</code></pre>

In your case, virtualenv is creating scripts like this:

<pre><code>#!/tmp/oh no/bin/python
</code></pre>

When the system tries to execute that, it will try to execute the command <code>/tmp/oh</code> with the arguments <code>no/bin/python</code> and <code>/tmp/test.py</code>. <code>/tmp/oh</code> does not exist, so it fails.

blocks|key|529909|text|关于原因，icktoofay是正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|529910|要在包含空格的目录中使用pip和virtualenv，请编辑/path/to/env/bin/pip，将顶部的shebang替换为#!/usr/bin/env+python+(如果您使用的是pypy，则替换为#!/usr/bin/env+pypy+)。|offset|length|style|CODE|529911|请注意，virtualenv会更改您的环境，以便/usr/bin/env+python引用由virtualenv定义的python。|529912|entityMap^0|0|U|K|1T|L|2W|J|0|O|J|1N|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$]]

icktoofay is correct about the cause.

To use pip with virtualenv in a directory with spaces, edit <code>/path/to/env/bin/pip</code>, replacing the shebang at the top with <code>#!/usr/bin/env python</code> (or <code>#!/usr/bin/env pypy</code> if you're using pypy).

Note that virtualenv changes your environment such that <code>/usr/bin/env python</code> refers to the <code>python</code> defined by the virtualenv.

blocks|key|746344|text|我在RedHat中得到了同样的错误。Python+2.7.3是我自己配置和制作的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|746345|[root@Ifx+installer]#+pip+install+Django
-bash:+/usr/local/bin/pip:+/usr/local/bin/python2.7:+bad+interpreter:+Permission+denied|code-block|syntax|javascript|746346|解决方案:在/usr/local/bin/pip中，将第一行#!/usr/local/bin/python2.7替换为实际的Python路径#!/root/installer/Python-2.7.5/python|746347|entityMap^0|2|6|0|0|6|I|U|Q|1Y|11|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]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

I got the same error in <code>RedHat</code>. Python 2.7.3 is configured and made by myself.
<pre><code>[root@Ifx installer]# pip install Django
-bash: /usr/local/bin/pip: /usr/local/bin/python2.7: bad interpreter: Permission denied
</code></pre>
Solution: In <code>/usr/local/bin/pip</code>, replace first line <code>#!/usr/local/bin/python2.7</code> with your actual Python path <code>#!/root/installer/Python-2.7.5/python</code>

blocks|key|746373|text|对于遇到这个问题的人，我发现路径的长度也会导致问题，不使用任何空格(Ubuntu+12.04)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|746374|virtualenv+/home/user/some/very/longer/path/without/spaces/etc/venv|code-block|syntax|javascript|746375|失败，而|746376|virtualenv+/home/user/some/very/long/path/without/spaces/etc/venv|746377|工作得很好，看下面Alex的评论|746378|entityMap^0|0|0|0|0|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|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For those running into this issue, I discovered that the length of the path could cause issues as well, without using any spaces (Ubuntu 12.04):

<pre><code>virtualenv /home/user/some/very/longer/path/without/spaces/etc/venv
</code></pre>

failed, while

<pre><code>virtualenv /home/user/some/very/long/path/without/spaces/etc/venv
</code></pre>

worked just fine, see Alex's comment below

blocks|key|746421|text|当我遇到同样的问题时，我在谷歌搜索中发现了这一点，并发现这一点非常有用。virtualenv现在有一个--relocatable标志，它会将shebang命令重写为#!/usr/bin/env+<the_python_version_you_used_to_create_the_virtualenv>。它确实附带了一些警告，因此请务必阅读文档以了解其中的含义：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|746422|https://virtualenv.pypa.io/en/stable/userguide/#making-environments-relocatable|746423|您需要使用与创建时相同的语法来重新定位virtualenv，否则python版本可能会被覆盖。这将像预期的那样工作。|746424|virtualenv+--python=python3.5+env-test
virtualenv+--relocatable+--python=python3.5+env-test|code-block|syntax|javascript|746425|然而这将导致#!/usr/bin/env+python2.7+(至少在我的本地环境中)...|746426|virtualenv+--python==python3.5+env-test
virtualenv+--relocatable+env-test|746427|entityMap|0|LINK|mutability|MUTABLE|url^0|10|A|1F|D|2A|1X|0|0|27|0|0|0|0|6|O|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1F|8|@]|D|@]|E|$M|N]]|$1|S|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|G]]]]

I found this from a Google search while experiencing the same problem and found this to be very useful. <code>virtualenv</code> now has a <code>--relocatable</code> flag that will rewrite the shebang command to <code>#!/usr/bin/env &lt;the_python_version_you_used_to_create_the_virtualenv&gt;</code>. It does come with some caveats, so be sure to read the documentation to understand the implications:

<a href="https://virtualenv.pypa.io/en/stable/userguide/#making-environments-relocatable" rel="nofollow noreferrer">https://virtualenv.pypa.io/en/stable/userguide/#making-environments-relocatable</a>

You need to use the same syntax to relocate the virtualenv as you did when creating it, otherwise the python version may be overwritten. This will work as expected...

<pre><code>virtualenv --python=python3.5 env-test
virtualenv --relocatable --python=python3.5 env-test
</code></pre>

whereas this will result in <code>#!/usr/bin/env python2.7</code> (at least on my local environment)...

<pre><code>virtualenv --python==python3.5 env-test
virtualenv --relocatable env-test
</code></pre>

blocks|key|746498|text|对于我的情况，停用环境，source+bin/activate就会再次工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|746499|似乎我的文件夹内容具有与virtualenv生成的相同的子文件夹名，如bin，lib等。在复制到我的文件后，重新激活环境，让virtualenv更新新信息。|746500|entityMap^0|C|J|0|C|A|1Q|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

For my case, deactivate the environment and <code>source bin/activate</code> again works. 

It seems my folder content has same subfolder names as generated by <code>virtualenv</code>, such as bin, lib etc. And after copy in my files, reactivate the environment let <code>virtualenv</code> to update new information.

blocks|key|530101|text|在Python+3.7上，我对此没有任何问题，但当我不得不使用Python+3.6时，我确实遇到了一个问题。我在Github上找到的最简单的变通方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|530102|而不是：|530103|pip+install+-r+requirements.txt|code-block|syntax|javascript|530104|我使用：|530105|python+env/bin/pip+install+-r+requirements.txt|530106|因此，您实际上直接指向虚拟环境目录中的pip文件。当然，在尝试此操作之前，您需要先激活它。希望这对来到这里的人有所帮助！|530107|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

On Python 3.7 I didn't have any issues with this but when I had to use Python 3.6 I did have an issue. The most easy work-around I found on Github was this:

Instead of:

<pre><code>pip install -r requirements.txt
</code></pre>

I use:

<pre><code>python env/bin/pip install -r requirements.txt
</code></pre>

So you actually directly point to the pip file within your virtual environment directory. Of course you need to activate it first before trying this. Hope this helps someone who comes here!

blocks|key|530133|text|如果它是在windows上，它可能是由于dll更改(由其他软件)造成的，安装openSSL可以修复它。https://slproweb.com/products/Win32OpenSSL.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|530134|它会自动将dll更新到其较新的版本。|530135|entityMap|0|LINK|mutability|MUTABLE|url|https://slproweb.com/products/Win32OpenSSL.html^0|1F|1B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

If it's on windows, it can be caused due to dll changes(by other software)
Installing openSSL would fix it.
<a href="https://slproweb.com/products/Win32OpenSSL.html" rel="nofollow noreferrer">https://slproweb.com/products/Win32OpenSSL.html</a>
It will automatically renew dll to its newer versions.

Below is the error I get when I run <code>pip</code>: 

<pre><code>serkan$ rm -r mysite
serkan$ pwd
/Users/serkan/Desktop/Python Folder
serkan$ virtualenv mysite 
New python executable in mysite/bin/python
Installing setuptools............done.
Installing pip...............done.
serkan$ source mysite/bin/activate
(mysite)serkan$ pip install pinax
-bash: /Users/serkan/Desktop/Python Folder/mysite/bin/pip: "/Users/serkan/Desktop/Python: bad interpreter: No such file or directory
(mysite)serkan$ python pip install pinax
python: can't open file 'pip': [Errno 2] No such file or directory
(mysite)serkan$ python pip install Pinax
python: can't open file 'pip': [Errno 2] No such file or directory
(mysite)serkan$ python pip install Pinax
python: can't open file 'pip': [Errno 2] No such file or directory
(mysite)serkan$ python pip install Pinax
python: can't open file 'pip': [Errno 2] No such file or directory
(mysite)serkan$ python pip 
python: can't open file 'pip': [Errno 2] No such file or directory
(mysite)serkan$ pip
-bash: /Users/serkan/Desktop/Python Folder/mysite/bin/pip: "/Users/serkan/Desktop/Python: bad interpreter: No such file or directory
(mysite)serkan$ pip install Pinax
-bash: /Users/serkan/Desktop/Python Folder/mysite/bin/pip: "/Users/serkan/Desktop/Python: bad interpreter: No such file or directory
(mysite)serkan$ 
</code></pre>

Can't install via pip with Virtualenv

解释器

Django

Python

Ubuntu

下面是我运行pip时得到的错误：serkan$ rm -r mysiteserkan$ pwd/Users/serkan/Desktop/Python Folderserkan$ virtualenv mysite New python executable in mysite/bin/pythonInstalling...

问无法使用Virtualenv通过pip进行安装
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使用Virtualenv通过pip进行安装EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法使用Virtualenv通过pip进行安装
EN