步骤1:冻结要求并对现有环境进行备份

pip freeze > requirements.txt
deactivate
mv env env_old

步骤2:安装Python 3.7并激活虚拟环境

sudo apt-get install python3.7-venv
python3.7 -m venv env
source env/bin/activate
python --version

步骤3:安装需求

sudo apt-get install python3.7-dev
pip3 install -r requirements.txt

给每个有问题的人

错误:命令'['/Users/me/Sites/site/venv3/bin/python3'， '-Im'， 'ensurepip'， '——upgrade'， '——default-pip']'返回非零退出状态1。

你必须安装python3.6-venv

 sudo apt-get install python3.6-venv

如果你碰巧使用Python 3.3+附带的venv模块，它支持——upgrade选项。 根据文档:

升级环境目录以使用此版本的Python，假设Python已在适当位置升级

python3 -m venv --upgrade ENV_DIR

步骤1:冻结要求并对现有环境进行备份

pip freeze > requirements.txt
deactivate
mv env env_old

步骤2:安装Python 3.7并激活虚拟环境

sudo apt-get install python3.7-venv
python3.7 -m venv env
source env/bin/activate
python --version

步骤3:安装需求

sudo apt-get install python3.7-dev
pip3 install -r requirements.txt

I moved my home directory from one mac to another (Mountain Lion to Yosemite) and didn't realize about the broken virtualenv until I lost hold of the old laptop. I had the virtualenv point to Python 2.7 installed by brew and since Yosemite came with Python 2.7, I wanted to update my virtualenv to the system python. When I ran virtualenv on top of the existing directory, I was getting OSError: [Errno 17] File exists: '/Users/hdara/bin/python2.7/lib/python2.7/config' error. By trial and error, I worked around this issue by removing a few links and fixing up a few more manually. This is what I finally did (similar to what @Rockalite did, but simpler):

cd <virtualenv-root>
rm lib/python2.7/config
rm lib/python2.7/lib-dynload
rm include/python2.7
rm .Python
cd lib/python2.7
gfind . -type l -xtype l | while read f; do ln -s -f /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/${f#./} $f; done

在此之后，我可以在现有目录上运行virtualenv。

在OS X或macOS上使用Homebrew安装和升级Python3，我必须在python -m venv——upgrade ENV_DIR工作之前删除符号链接。

我在upgrade_python3.sh中保存了以下文件，这样我就能记住几个月后我需要再次这样做:

brew upgrade python3
find ~/.virtualenvs/ -type l -delete
find ~/.virtualenvs/ -type d -mindepth 1 -maxdepth 1 -exec python3 -m venv --upgrade "{}" \;

更新:虽然这似乎工作得很好，当我运行py。测试它给出了一个错误。最后，我只是根据需求文件重新创建了环境。