blocks|key|3450792|text|当您以virtualenv身份创建virtualenv，然后在virtualenv中没有sudo的情况下操作时，可能会出现sudo权限问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3450793|正如你的问题的评论中所发现的，这里的解决方案是在没有sudo的情况下创建+virtualenv，以便能够使用work+(esp.write)在没有sudo的情况下。|3450794|entityMap^0|3|A|H|A|V|A|18|4|1P|4|0|Q|4|11|A|21|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$]]

<code>virtualenv</code> permission problems might occur when you create the <code>virtualenv</code> as <code>sudo</code> and then operate without <code>sudo</code> in the <code>virtualenv</code>.

As found out in your question's comment, the solution here is to create the <code>virtualenv</code> without <code>sudo</code> to be able to work (esp. write) in it without <code>sudo</code>.

blocks|key|401912|text|解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|401913|如果您以root身份创建了virtualenv，请运行以下命令：|401914|sudo+chown+-R+your_username:your_username+path/to/virtuaelenv/|code-block|syntax|javascript|401915|这可能会解决您的问题。|401916|干杯|401917|entityMap^0|0|5|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|6|7|Y|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Solution:

If you created the virtualenv as root, run the following command:

<pre><code>sudo chown -R your_username:your_username path/to/virtuaelenv/
</code></pre>

This will probably fix your problem.

Cheers

blocks|key|3237685|text|在我的例子中，我使用的是mkvirtualenv，但没有告诉它我将使用python3。我得到了这个错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3237686|mkvirtualenv+hug
pip3+install+hug+-U

....
error:+could+not+create+'/usr/lib/python3.4/site-packages':+Permission+denied|code-block|syntax|javascript|3237687|在指定python3之后，它就可以工作了：|3237688|mkvirtualenv+--python=/usr/bin/python3+hug
pip3+install+hug+-U|3237689|entityMap^0|C|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

In my case, I was using <code>mkvirtualenv</code>, but didn't tell it I was going to be using python3. I got this error:

<pre><code>mkvirtualenv hug
pip3 install hug -U

....
error: could not create '/usr/lib/python3.4/site-packages': Permission denied
</code></pre>

It worked after specifying python3:

<pre><code>mkvirtualenv --python=/usr/bin/python3 hug
pip3 install hug -U
</code></pre>

blocks|key|405431|text|如果您使用root创建了虚拟环境，则使用以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|405432|sudo+su|code-block|syntax|javascript|405433|它将为您提供root访问权限，然后使用以下命令激活您的虚拟环境|405434|source+/root/.env/ENV_NAME/bin/activate|405435|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|$]]

If you created virtual environment using root then use this command

<pre><code>sudo su
</code></pre>

it will give you the root access and then activate your virtual environment using this

<pre><code>source /root/.env/ENV_NAME/bin/activate
</code></pre>

blocks|key|408203|text|我没有使用sudo创建我的virtualenv。所以塞巴斯蒂安的答案不适用于我。我的项目名为utils。我检查了utils目录，发现如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|408204|-rw-r--r--+++1+macuser++staff+++983++6+Jan+15:17+README.md
drwxr-xr-x+++6+root+++++staff+++204++6+Jan+14:36+utils.egg-info
-rw-r--r--+++1+macuser++staff++++31++6+Jan+15:09+requirements.txt|code-block|syntax|javascript|408205|如你所见，utils.egg-info归root所有，而不是macuser。这就是为什么它会给我permission+denied错误。我还必须删除/Users/macuser/.virtualenvs/armoury/lib/python2.7/site-packages/utils.egg-link，因为它也是由root创建的。在删除它们之后，我又做了一次pip+install+-e+.，它起作用了。|408206|entityMap^0|1A|5|1K|5|0|0|5|E|K|4|U|7|1C|H|22|26|4F|4|51|G|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$]]

I didn't create my virtualenv using sudo. So Sebastian's answer didn't apply to me. My project is called <code>utils</code>. I checked <code>utils</code> directory and saw this:

<pre><code>-rw-r--r-- 1 macuser staff 983 6 Jan 15:17 README.md
drwxr-xr-x 6 root staff 204 6 Jan 14:36 utils.egg-info
-rw-r--r-- 1 macuser staff 31 6 Jan 15:09 requirements.txt
</code></pre>

As you can see, <code>utils.egg-info</code> is owned by <code>root</code> not <code>macuser</code>. That is why it was giving me <code>permission denied</code> error. I also had to remove <code>/Users/macuser/.virtualenvs/armoury/lib/python2.7/site-packages/utils.egg-link</code> as it was created by <code>root</code> as well. I did <code>pip install -e .</code> again after removing those, and it worked.

blocks|key|405227|text|在使用pip之前，您没有激活虚拟环境。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|405228|使用以下命令尝试：|405229|$(your+venv+path)+.+bin/activate|code-block|syntax|javascript|405230|，然后在主文件夹上使用pip+-r+requirements.txt。|405231|entityMap^0|A|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

You did not activate the virtual environment before using pip.

Try it with: 

<pre><code>$(your venv path) . bin/activate
</code></pre>

And then use pip -r requirements.txt on your main folder

blocks|key|405437|text|我也曾在现有的虚拟环境中创建了一个新的venv后(意外地)发生过这种情况。诊断这种情况的一种简单方法是查看python的符号链接位置，即运行：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|405438|ls+-l+venv/bin/python|code-block|syntax|javascript|405439|并确保它指向适当的Python二进制文件。对于大多数系统，这将是/usr/bin/python或/usr/bin/python3。而如果它指向一个现有的虚拟环境，它将类似于/home/youruser/somedir/bin/python。如果是后者，那么我建议重新创建venv，同时确保您不在任何现有的virtualenv中(即运行deactivate+)。|405440|entityMap^0|1H|6|0|0|W|F|1C|G|2E|X|4N|A|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]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

I've also had this happen (by accident) after creating a new venv while inside an existing virtual environment. an easy way to diagnose this would be to see where the <code>python</code> is symlinked to, i.e. run:

<pre class="lang-sh prettyprint-override"><code>ls -l venv/bin/python
</code></pre>

and make sure it points to the appropriate Python binary. For most systems this will be <code>/usr/bin/python</code> or <code>/usr/bin/python3</code>. while if it points to an existing virtual environment it'll be something like <code>/home/youruser/somedir/bin/python</code>. if it's the latter than I'd suggest recreating the venv while making sure that you aren't "inside" any existing virtualenv (i.e. run <code>deactivate</code> )

blocks|key|408232|text|在创建virtualenv时，如果使用sudo，则使用根privileges.So创建目录，当您尝试以非sudo用户身份安装包时，您将没有权限安装到该目录中。因此，始终创建不带sudo虚拟环境和不带sudo的安装。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|408233|您还可以将全局python上安装的包复制到virtualenv。|408234|cp+-r+/lib/python/site-packages/*+virtualenv/lib/python/site-packages/|code-block|syntax|javascript|408235|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

While creating virtualenv if you use sudo the directory is created with root privileges.So when you try to install a package with non-sudo user you won't have permission to install into it.
So always create virtualenv without sudo and install without sudo.

You can also copy packages installed on global python to virtualenv. 

<pre><code>cp -r /lib/python/site-packages/* virtualenv/lib/python/site-packages/
</code></pre>

blocks|key|3237744|text|尝试：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3237745|.+venv/bin/activate|code-block|syntax|javascript|3237746|或：|3237747|source+venv/bin/activate|3237748|entityMap^0|0|3|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

Try:
<pre><code>. venv/bin/activate
</code></pre>
Or:
<pre><code>source venv/bin/activate
</code></pre>

I attempt to deploy a Python package with <code>pip</code> in a virtual environment on an Ubuntu machine, but encounter a permission-related issue. For example:

<pre><code>(TestVirtualEnv)test@testServer:~$ pip install markdown2
</code></pre>

terminates by:

<blockquote>
 error: could not create '/home/test/virtualenvs/TestVirtualEnv/lib/python3.3/site-packages/markdown2.py': Permission denied
</blockquote>

I can't <code>sudo</code>, since it will install the package globally, and not within the virtual environment. I <code>chown</code>ed <code>site-packages</code>; <code>ls</code> shows only directories related to <code>easy_install</code>, <code>pip</code> and <code>setuptools</code>, and nothing related to Markdown.

How to deploy a package in a virtual environment with <code>pip</code> without encountering permission-related errors?

How to avoid "Permission denied" when using pip with virtualenv

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我尝试在Ubuntu机器上的虚拟环境中使用pip部署Python包，但遇到了与权限相关的问题。例如：(TestVirtualEnv)test@testServer:~$ pip install markdown2终止于：错误:无法创建权限被拒绝的'/home/test/virtualenvs/TestVirtualEnv/lib/python3.3/site-packages/markdown2.

问在使用pip和virtualenv时，如何避免“权限被拒绝”
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用pip和virtualenv时，如何避免“权限被拒绝”EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用pip和virtualenv时，如何避免“权限被拒绝”
EN