blocks|key|4631215|text|It+appears解决此问题的正确方法是运行|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4631216|+pip+install+--upgrade+virtualenv|code-block|syntax|javascript|4631217|在您使用Homebrew升级python之后。|4631218|对于任何安装了python之类的东西的公式来说，这应该是一个通用的过程，python有自己的包管理系统。安装brew+install+python时，需要安装python、pip、easy_install和virtualenv等。因此，如果这些工具可以自我更新，最好在将Homebrew作为问题的根源之前尝试这样做。|style|CODE|4631219|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Homebrew/homebrew/issues/29247^0|0|A|0|0|0|0|1I|J|27|6|2E|3|2I|C|2V|A|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|12|8|@$A|13|B|14|M|N]|$A|15|B|16|M|N]|$A|17|B|18|M|N]|$A|19|B|1A|M|N]|$A|1B|B|1C|M|N]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

<a href="https://github.com/Homebrew/homebrew/issues/29247" rel="noreferrer">It appears</a> the proper way to resolve this issue is to run

<pre><code> pip install --upgrade virtualenv
</code></pre>

after you have upgraded python with Homebrew. 

This should be a general procedure for any formula that installs something like python, which has it's own package management system. When you install <code>brew install python</code>, you install <code>python</code> and <code>pip</code> and <code>easy_install</code> and <code>virtualenv</code> and so on. So, if those tools can be self-updated, it's best to try to do so before looking to Homebrew as the source of problems.

blocks|key|4631378|text|我找到了问题的解决方案here，所以所有的功劳都归功于作者。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4631379|要点是，当您创建一个virtualenv时，会创建许多指向Homebrew安装的Python的符号链接。|4631380|这里有一个例子：|4631381|$+ls+-la+~/.virtualenvs/my-virtual-env
...
lrwxr-xr-x++1+ryan+staff+++78+Jun+25+13:21+.Python+->+/usr/local/Cellar/python/2.7.7/Frameworks/Python.framework/Versions/2.7/Python
...|code-block|syntax|javascript|4631382|当您使用Homebrew升级Python，然后运行brew+cleanup时，virtualenv中的符号链接指向不再存在的路径(因为Homebrew删除了它们)。|style|CODE|4631383|符号链接需要指向新安装的Python：|4631384|lrwxr-xr-x++1+ryan+staff+++78+Jun+25+13:21+.Python+->+/usr/local/Cellar/python/2.7.8_1/Frameworks/Python.framework/Versions/2.7/Python|4631385|解决方案是删除virtualenv中的符号链接，然后重新创建它们：|4631386|find+~/.virtualenvs/my-virtual-env/+-type+l+-delete
virtualenv+~/.virtualenvs/my-virtual-env|4631387|在删除链接之前，最好先检查一下哪些链接将被删除：|4631388|find+~/.virtualenvs/my-virtual-env/+-type+l|4631389|在我看来，只删除断开的符号链接会更好。您可以使用GNU+find来实现这一点。|4631390|gfind+~/.virtualenvs/my-virtual-env/+-type+l+-xtype+l+-delete|4631391|如果你还没有GNU+find，你可以在Homebrew中安装它：|4631392|brew+install+findutils|4631393|请注意，默认情况下，与Homebrew一起安装的GNU程序倾向于以字母g作为前缀。这是为了避免遮蔽OS附带的find二进制文件。|4631394|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20150206132233/https://wirtel.be/posts/en/2014/07/29/fix_virtualenv_python_brew/^0|B|4|0|0|0|0|0|P|C|0|0|0|0|0|0|0|S|4|0|0|A|4|0|0|Z|1|1I|4|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|D|3|E|5|6|7|1O|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1P|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1Q|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1R|8|@$A|1S|B|1T|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1U|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1V|8|@]|9|@]|C|$K|L]]|$1|U|3|V|5|6|7|1W|8|@]|9|@]|C|$]]|$1|W|3|X|5|J|7|1X|8|@]|9|@]|C|$K|L]]|$1|Y|3|Z|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|10|3|11|5|J|7|1Z|8|@]|9|@]|C|$K|L]]|$1|12|3|13|5|6|7|20|8|@$A|21|B|22|O|P]]|9|@]|C|$]]|$1|14|3|15|5|J|7|23|8|@]|9|@]|C|$K|L]]|$1|16|3|17|5|6|7|24|8|@$A|25|B|26|O|P]]|9|@]|C|$]]|$1|18|3|19|5|J|7|27|8|@]|9|@]|C|$K|L]]|$1|1A|3|1B|5|6|7|28|8|@$A|29|B|2A|O|P]|$A|2B|B|2C|O|P]]|9|@]|C|$]]|$1|1C|3|-4|5|6|7|2D|8|@]|9|@]|C|$]]]|1D|$1E|$5|1F|1G|1H|C|$1I|1J]]]]

I found the solution to the problem <a href="https://web.archive.org/web/20150206132233/https://wirtel.be/posts/en/2014/07/29/fix_virtualenv_python_brew/" rel="noreferrer">here</a>, so all credit goes to the author.

The gist is that when you create a virtualenv, many symlinks are created to the Homebrew installed Python.

Here is one example:

<pre><code>$ ls -la ~/.virtualenvs/my-virtual-env
...
lrwxr-xr-x 1 ryan staff 78 Jun 25 13:21 .Python -&gt; /usr/local/Cellar/python/2.7.7/Frameworks/Python.framework/Versions/2.7/Python
...
</code></pre>

When you upgrade Python using Homebrew and then run <code>brew cleanup</code>, the symlinks in the virtualenv point to paths that no longer exist (because Homebrew deleted them).

The symlinks needs to point to the newly installed Python:

<pre><code>lrwxr-xr-x 1 ryan staff 78 Jun 25 13:21 .Python -&gt; /usr/local/Cellar/python/2.7.8_1/Frameworks/Python.framework/Versions/2.7/Python
</code></pre>

The solution is to remove the symlinks in the virtualenv and then recreate them:

<pre><code>find ~/.virtualenvs/my-virtual-env/ -type l -delete
virtualenv ~/.virtualenvs/my-virtual-env
</code></pre>

It's probably best to check what links will be deleted first before deleting them:

<pre><code>find ~/.virtualenvs/my-virtual-env/ -type l
</code></pre>

In my opinion, it's even better to only delete broken symlinks. You can do this using GNU <code>find</code>:

<pre><code>gfind ~/.virtualenvs/my-virtual-env/ -type l -xtype l -delete
</code></pre>

You can install GNU <code>find</code> with Homebrew if you don't already have it:

<pre><code>brew install findutils
</code></pre>

Notice that by default, GNU programs installed with Homebrew tend to be prefixed with the letter <code>g</code>. This is to avoid shadowing the <code>find</code> binary that ships with OS X.

blocks|key|4631450|text|在尝试了一些方法之后，这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4631451|转到您的virtualenv目录(但不要运行workon)：|4631452|cd+~/.virtualenv/name_of_broken_venv|code-block|syntax|javascript|4631453|现在删除这些文件：|4631454|rm+-rf+.Python+bin/python*+lib/python2.7/*+include/python2.7|4631455|然后，要重新构建venv，运行：|4631456|virtualenv+.
workon+name_of_broken_venv
pip+freeze|4631457|现在，您应该会再次看到已安装软件包的列表。|4631458|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

After trying a few things, this worked for me:

go to your virtualenv directory (but don't run workon):

<pre><code>cd ~/.virtualenv/name_of_broken_venv
</code></pre>

Now delete these files:

<pre><code>rm -rf .Python bin/python* lib/python2.7/* include/python2.7
</code></pre>

Then to rebuild your venv, run:

<pre><code>virtualenv .
workon name_of_broken_venv
pip freeze
</code></pre>

You should now see a list of your installed packages again.

blocks|key|4631517|text|更新版本@Chris+Wedgwood对保留site-packages+(保留已安装的软件包)的回答|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4631518|cd+~/.virtualenv/name_of_broken_venv


mv+lib/python2.7/site-packages+./++++
rm+-rf+.Python+bin+lib+include
virtualenv+.
rm+-rf+lib/python2.7/site-packages
mv+./site-packages+lib/python2.7/|code-block|syntax|javascript|4631519|entityMap^0|4|F|M|D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

A update version <code>@Chris Wedgwood</code>'s answer for keeping <code>site-packages</code> (keeping packages installed)

<pre><code>cd ~/.virtualenv/name_of_broken_venv


mv lib/python2.7/site-packages ./ 
rm -rf .Python bin lib include
virtualenv .
rm -rf lib/python2.7/site-packages
mv ./site-packages lib/python2.7/
</code></pre>

blocks|key|4631541|text|使用Python+2.7.10。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4631542|只有一个命令virtualenv+path-to-env就可以做到这一点。documentation|offset|length|style|CODE|4631543|$+virtualenv+path-to-env
Overwriting+path-to-env/lib/python2.7/orig-prefix.txt+with+new+content
New+python+executable+in+path-to-env/bin/python2.7
Also+creating+executable+in+path-to-env/bin/python
Installing+setuptools,+pip,+wheel...done.|code-block|syntax|javascript|4631544|entityMap|0|LINK|mutability|MUTABLE|url|https://virtualenv.pypa.io/en/stable/userguide/#usage^0|0|6|M|11|D|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|H|3|I|5|J|7|11|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Using Python 2.7.10.

A single command <code>virtualenv path-to-env</code> does it. <a href="https://virtualenv.pypa.io/en/stable/userguide/#usage" rel="nofollow noreferrer">documentation</a>

<pre><code>$ virtualenv path-to-env
Overwriting path-to-env/lib/python2.7/orig-prefix.txt with new content
New python executable in path-to-env/bin/python2.7
Also creating executable in path-to-env/bin/python
Installing setuptools, pip, wheel...done.
</code></pre>

blocks|key|125471|text|如果你已经破解了python3，那就试试brew+upgrade+python3吧，它帮我修复了它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|125472|entityMap^0|K|K|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you've busted python3 just try <code>brew upgrade python3</code> that fixed it for me.

blocks|key|4631639|text|如果这是由升级了Python的brew+upgrade引起的，并且你可以降级到以前的版本，可以试试brew+switch+python+[previous+version]，例如brew+switch+python+3.6.5。From+here.|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4631640|entityMap|0|LINK|mutability|MUTABLE|url|https://apple.stackexchange.com/a/326608/43900^0|F|C|1D|11|2H|O|36|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

If this was caused by a <code>brew upgrade</code> that upgraded its Python, and you're ok with downgrading to the previous version, try <code>brew switch python [previous version]</code>, eg <code>brew switch python 3.6.5</code>. <a href="https://apple.stackexchange.com/a/326608/43900">From here.</a>

blocks|key|125557|text|简单地升级python3对我来说很管用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|125558|brew+upgrade+python3|code-block|syntax|javascript|125559|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|$]]

Simply upgrading python3 worked for me:

<pre><code>brew upgrade python3
</code></pre>

blocks|key|4631699|text|修复它的方法就是卸载python3和pipenv，然后重新安装它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4631700|brew+uninstall+pipenv
brew+uninstall+python3
brew+install+python3+
brew+install+pipenv|code-block|syntax|javascript|4631701|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|$]]

What fixed it for me was just uninstalling python3 and pipenv then reinstalling them.

<pre><code>brew uninstall pipenv
brew uninstall python3
brew install python3 
brew install pipenv
</code></pre>

blocks|key|125648|text|对于我(一个MacOS用户)来说，问题是brew更新了Python和virtualenvs链接到被删除的旧版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|125649|我们可以通过以下方式检查和修复它|125650|>>+ls+-al+~/.virtualenvs/<your-virtual-env>/.Python
.Python+->+/usr/local/Cellar/python/<old-version>/Frameworks/Python.framework/Versions/3.7/Python
>>+rm+~/.virtualenvs/<your-virtual-env>/.Python
>>+ln+-s++/usr/local/Cellar/python/<new-version>/Frameworks/Python.framework/Versions/3.7/Python+~/.virtualenvs/<your-virtual-env>/.Python|code-block|syntax|javascript|125651|entityMap^0|K|4|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

The problem for me(a MacOS user) is that <code>brew</code> updated the Python and virtualenvs links to the old version which was deleted.

We can check and fix it by

<pre><code>&gt;&gt; ls -al ~/.virtualenvs/&lt;your-virtual-env&gt;/.Python
.Python -&gt; /usr/local/Cellar/python/&lt;old-version&gt;/Frameworks/Python.framework/Versions/3.7/Python
&gt;&gt; rm ~/.virtualenvs/&lt;your-virtual-env&gt;/.Python
&gt;&gt; ln -s /usr/local/Cellar/python/&lt;new-version&gt;/Frameworks/Python.framework/Versions/3.7/Python ~/.virtualenvs/&lt;your-virtual-env&gt;/.Python
</code></pre>

blocks|key|4631794|text|我尝试了最好的几种方法，但对我来说，它们都不起作用，因为我试图让毒素起作用。最终起作用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4631795|sudo+pip+install+tox|code-block|syntax|javascript|4631796|即使毒理已经安装好了。输出以以下方式终止：|4631797|Successfully+built+filelock
Installing+collected+packages:+py,+pluggy,+toml,+filelock,+tox
Successfully+installed+filelock-3.0.10+pluggy-0.11.0+py-1.8.0+toml-0.10.0+tox-3.9.0|4631798|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|$]]

I tried the top few methods, but they didn't work, for me, which were trying to make tox work. What eventually worked was:

<pre><code>sudo pip install tox
</code></pre>

even if tox was already installed. The output terminated with:

<pre><code>Successfully built filelock
Installing collected packages: py, pluggy, toml, filelock, tox
Successfully installed filelock-3.0.10 pluggy-0.11.0 py-1.8.0 toml-0.10.0 tox-3.9.0
</code></pre>

blocks|key|125711|text|任何正在使用pipenv的人(您应该这样做！)可以简单地使用这两个命令-无需激活venv：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|125712|rm+-rf+`pipenv+--venv`+#+remove+the+broken+venv
pipenv+install+--dev+++#+reinstall+the+venv+from+pipfile+|code-block|syntax|javascript|125713|entityMap|0|LINK|mutability|MUTABLE|url|https://pipenv.kennethreitz.org/en/latest/^0|6|6|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Anyone who is using <a href="https://pipenv.kennethreitz.org/en/latest/" rel="nofollow noreferrer">pipenv</a> (and you should!) can simply use these two commands — without having the venv activated:

<pre><code>rm -rf `pipenv --venv` # remove the broken venv
pipenv install --dev # reinstall the venv from pipfile 
</code></pre>

blocks|key|4631859|text|由于python的Homebrew重装(从而破坏了符号链接)以及我之前做的一些"sudo+pip+install“，我有一个损坏的虚拟环境。微众的提示对修复问题非常有帮助，而不必重新安装软件包。对于混合权限问题，我还必须执行以下操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4631860|sudo+chown+-R+my_username库/python2.7/site-packages|4631861|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had a broken virtual env due to a Homebrew reinstall of python (thereby broken symlinks) and also a few "sudo pip install"s I had done earlier. Weizhong's tips were very helpful in fixing the issues without having to reinstall packages. I also had to do the following for the mixed permissions problem.

sudo chown -R my_username lib/python2.7/site-packages

blocks|key|125783|text|Virtualenv被破坏了。有时简单的方法是删除venv文件夹并重新创建virutalenvs。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|125784|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Virtualenvs are broken. Sometimes simple way is to delete venv folders and recreate virutalenvs.

blocks|key|4631923|text|我也遇到过类似的问题，我只需使用virtualenv+.重新构建虚拟环境即可解决|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4631924|entityMap^0|G|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had a similar issue and i solved it by just rebuilding the virtual environment with <code>virtualenv .</code>

blocks|key|125857|text|如果您使用的是pipenv，只需执行pipenv+--rm就可以解决问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|125858|entityMap^0|I|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you using pipenv, just doing <code>pipenv --rm</code> solves the problem.

blocks|key|4632015|text|我肯定我来晚了，但我想说，这个问题的解决比这里讨论的要简单得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4632016|您可以轻松地重新生成虚拟环境，而无需删除/编辑任何内容。假设您的损坏环境名为env_to_fix，您只需执行以下操作：|offset|length|style|CODE|4632017|mkvirtualenv+env_to_fix|code-block|syntax|javascript|4632018|这将重新生成链接并修复环境，而无需将当前状态转储到某个位置并将其恢复。|4632019|entityMap^0|0|12|A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I am sure I am late to the party but I want to say that the resolution of this problem is much simpler than discussed here.

You can easily regenerate the virtual environment without having to delete/edit anything. Assuming that your broken environment is called <code>env_to_fix</code> you can just to the following:

<pre><code>mkvirtualenv env_to_fix
</code></pre>

This will regenerate the links and fix the environment without the need to dump the current status somewhere and restore it.

blocks|key|4632045|text|当我在mac上将python运行时从2指向3，将别名python指向python+3路径时，我遇到了同样的问题。然后，我重新创建一个新的virtualenv，并重新安装我的项目所需的那些包。对于我的用例，我有一个python程序写入google+sheet。清理一些与python2实现和wa不同的包，事情又开始工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4632046|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I came across the same issue when I was pointing my python run time from 2 to 3 on my mac, pointing the alias python to python 3 path. I then recreate a new virtualenv and re-install those packages i need for my project. For my use case i have had a python program writing to google sheet. Clean up a few packages that are different from python 2 implementation and wa la, things started working again.

blocks|key|4632100|text|在我的OSX+Catalina上升级brew后，我也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4632101|在尝试了一大堆东西之后，我发现以下是最好也是最简单的解决方案。|4632102|首先，删除虚拟环境。(可选)|4632103|find+myvirtualenv+-type+l+-delete|code-block|syntax|javascript|4632104|然后重新创建新的虚拟环境|4632105|virtualenv+myvirtualenv|4632106|参考：https://www.jeremycade.com/python/osx/homebrew/2015/03/02/fixing-virtualenv-after-a-python-upgrade/|offset|length|4632107|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jeremycade.com/python/osx/homebrew/2015/03/02/fixing-virtualenv-after-a-python-upgrade/^0|0|0|0|0|0|0|3|2R|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|16|8|@]|9|@$Q|17|R|18|1|19]]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I was facing the same issue after upgrading brew on my OSX Catalina.

After trying bunch of stuffs, I find the following is the best and easy solution.

At first, delete the virtual env. (Optional)

<pre><code>find myvirtualenv -type l -delete
</code></pre>

then recreate a new virtualenv

<pre><code>virtualenv myvirtualenv
</code></pre>

Reference: <a href="https://www.jeremycade.com/python/osx/homebrew/2015/03/02/fixing-virtualenv-after-a-python-upgrade/" rel="nofollow noreferrer">https://www.jeremycade.com/python/osx/homebrew/2015/03/02/fixing-virtualenv-after-a-python-upgrade/</a>

blocks|key|4632164|text|因为我已经冻结了requirements.txt文件，所以有很多方法，但其中一种对我有效，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4632165|因此，使用deactivate+cd+..+rm+-r+old_virtual_environment使用以下命令删除旧虚拟环境|offset|length|style|CODE|4632166|要使用pip安装virtualenv+python包，请使用pip+install+virtualenv|4632167|然后使用virtualenv+--version检查是否正确安装|4632168|使用cd+project_directory跳转到项目目录|4632169|现在使用下面的virtualenv+name_of_new_virtual_environment在项目目录中创建新的虚拟环境|4632170|现在使用source+name_of_new_virtual_environment/bin/activate激活新创建的虚拟环境|4632171|现在使用以下命令安装所有项目依赖项使用pip+install+-r+requirements.txt|4632172|entityMap^0|0|5|A|G|5|M|T|0|U|M|0|4|K|0|2|K|0|7|16|0|4|1F|0|J|V|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|U|$]]

So there are many ways but one which worked for me is as follows since I already had my requirements.txt file freeze.
So delete old virtual environment with following command
use
<code>deactivate</code>
<code>cd ..</code>
<code>rm -r old_virtual_environment</code>
to install virtualenv python package with pip
use <code>pip install virtualenv</code>
then check if it's installed correctly
use <code>virtualenv --version</code>
jump to your project directory
use <code>cd project_directory</code>
now create new virtual environment inside project directory using following
use <code>virtualenv name_of_new_virtual_environment</code>
now activate newly created virtual environment
use <code>source name_of_new_virtual_environment/bin/activate</code>
now install all project dependencies using following command
use <code>pip install -r requirements.txt</code>

blocks|key|4632237|text|当您在新创建的virtualenv上遇到此问题时，可能是由brew安装的python版本“未链接”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4632238|例如，您可以通过运行：brew+link+python@3.8+(但指定您的speficic+python版本)来修复此问题|offset|length|style|CODE|4632239|你也可以运行brew+doctor，它会告诉你是否有未链接的东西以及如何修复它。|4632240|entityMap^0|0|B|K|0|6|B|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]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

When you are running into this issue on a freshly created virtualenv, it might be that your python version installed by brew is &quot;unlinked&quot;.
You can fix this for example by running: <code>brew link python@3.8</code>
(but specify your speficic python version)
You can also run <code>brew doctor</code>, it will tell you if you have unlinked stuff and how to fix this.

I recently installed a bunch of dotfiles on my Mac along with some other applications (I changed to iTerm instead of Terminal, and Sublime as my default text editor) but ever since, all my virtual environments have stopped working, although their folders inside .virtualenvs are still there and they give the following error whenever I try to run anything in them:

<pre><code>dyld: Library not loaded: @executable_path/../.Python
 Referenced from: /Users/[user]/.virtualenvs/modclass/bin/python
 Reason: image not found
Trace/BPT trap: 5
</code></pre>

I have removed all the files related to dotfiles and have restored my .bash_profile to what it was before, but the problem persists. Is there any way to diagnose the problem or solve it in an easy way (e.g. not requiring to create all the virtualenvs all over again)?

Broken references in Virtualenvs

Python

MacOS

我最近在我的苹果电脑上安装了一堆点文件和其他一些应用程序(我改用iTerm而不是终端，Sublime作为我的默认文本编辑器)，但从那以后，我所有的虚拟环境都停止了工作，尽管它们在.virtualenvs中的文件夹仍然存在，每当我试图在其中运行任何东西时，它们都会显示以下错误：dyld: Library not load...

问Virtualenvs中损坏的引用
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Virtualenvs中损坏的引用EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Virtualenvs中损坏的引用
EN