blocks|key|843473|text|我总是安装virtualenvwrapper来帮助解决问题。在shell提示符下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843474|pip+install+virtualenvwrapper|code-block|syntax|javascript|843475|在virtualenvwrapper文档中记录了一种方法--+cpvirtualenv，这就是你要做的。确保您已离开环境并返回到shell提示符。使用所需的名称键入以下内容：|offset|length|843476|cpvirtualenv+oldenv+newenv|843477|然后，如果有必要：|843478|rmvirtualenv+oldenv|843479|要转到新环境，请执行以下操作：|843480|workon+newenv|843481|entityMap|0|LINK|mutability|MUTABLE|url|https://virtualenvwrapper.readthedocs.org/en/latest/command_ref.html?highlight=cpvirtualenv#cpvirtualenv^0|0|0|V|C|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|L|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

I always install virtualenvwrapper to help out. From the shell prompt:

<pre><code>pip install virtualenvwrapper
</code></pre>

There is a way documented in the virtualenvwrapper documents - <a href="https://virtualenvwrapper.readthedocs.org/en/latest/command_ref.html?highlight=cpvirtualenv#cpvirtualenv" rel="noreferrer">cpvirtualenv</a>
This is what you do. Make sure you are out of your environment and back to the shell prompt. Type in this with the names required:

<pre><code>cpvirtualenv oldenv newenv
</code></pre>

And then, if necessary:

<pre><code>rmvirtualenv oldenv
</code></pre>

To go to your newenv:

<pre><code>workon newenv
</code></pre>

blocks|key|627807|text|另一种方法是virtualenv-clone，它对我来说多次都没有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|627808|pip+install+virtualenv-clone
virtualenv-clone+old-dir/env+new-dir/env|code-block|syntax|javascript|627809|entityMap|0|LINK|mutability|MUTABLE|url|https://pypi.python.org/pypi/virtualenv-clone^0|6|G|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]]]]

Yet another way to do it that worked for me many times without problems is <a href="https://pypi.python.org/pypi/virtualenv-clone" rel="noreferrer">virtualenv-clone</a>:

<pre><code>pip install virtualenv-clone
virtualenv-clone old-dir/env new-dir/env
</code></pre>

blocks|key|627873|text|在您的项目文件夹中运行以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627874|cd+bin
sed+-i+'s/old_dir_name/new_dir_name/g'+*|code-block|syntax|javascript|627875|别忘了停用和激活。|627876|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Run this inside your project folder:
<pre><code>cd bin
sed -i 's/old_dir_name/new_dir_name/g' *
</code></pre>
Don't forget to deactivate and activate.

blocks|key|627969|text|在Python+3.3%2B中内置venv|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627970|从Python3.3开始，virtualenv包作为venv模块内置到Python中。有一些细微的区别，其中之一是--relocatable选项已被删除。因此，通常最好是重新创建虚拟环境，而不是尝试移动它。See+this+answer获取有关如何执行此操作的更多信息。|offset|length|style|CODE|627971|想要移动而不仅仅是重建任何虚拟环境背后的目的是什么？虚拟环境旨在管理具有venv的模块/包的依赖性，使得它可以具有它所依赖的给定包或模块的不同和特定版本，并允许本地安装这些东西的位置。|627972|因此，包应该提供一种从头开始重新创建venv的方法。通常，这是通过一个requirements.txt文件来完成的，有时还是一个requirements-dev.txt文件，甚至是一个在安装/安装包本身时重新创建venv的脚本。|627973|可能会让人头疼的一个部分是，您可能需要特定版本的Python作为可执行文件，如果还没有的话，这很难自动化。然而，在重新创建现有的虚拟环境时，当创建新的虚拟环境时，可以简单地从现有的venv运行python。在此之后，通常只需使用pip重新安装requirements.txt文件中的所有依赖项：|627974|来自Windows上的Git+Bash：|627975|python+-m+venv+mynewvenv
source+myvenv/Scripts/activate
pip+install+-r+requirements.txt|code-block|syntax|javascript|627976|如果你有来自其他本地开发包的几个本地依赖项，因为你可能需要更新本地绝对路径，等等-尽管如果你将它们设置为正确的Python包，你可以从git库安装，从而通过将静态URL作为源来避免这个问题。|627977|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/58772116/6501141^0|0|D|A|Q|4|1L|D|2V|F|0|0|0|Z|G|1S|K|0|3D|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]|$D|18|E|19|F|G]|$D|1A|E|1B|F|G]]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|H|3|I|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1O|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1P|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

<h2>In Python 3.3+ with built-in venv</h2>
As of Python 3.3 the <code>virtualenv</code> package is now built-in to Python as the <code>venv</code> module. There are a few minor differences, one of which is the <code>--relocatable</code> option has been removed. As a result, it is normally best to recreate a virtual environment rather than attempt to move it. <a href="https://stackoverflow.com/a/58772116/6501141">See this answer</a> for more information on how to do that.
What is the purpose behind wanting to move rather than just recreate any virtual environment? A virtual environment is intended to manage the dependencies of a module/package with the venv so that it can have different and specific versions of a given package or module it is dependent on, and allow a location for those things to be installed locally.
As a result, a package should provide a way to recreate the venv from scratch. Typically this is done with a <code>requirements.txt</code> file and sometimes also a <code>requirements-dev.txt</code> file, and even a script to recreate the venv in the setup/install of the package itself.
One part that may give headaches is that you may need a particular version of Python as the executable, which is difficult to automate, if not already present. However, when recreating an existing virtual environment, one can simply run python from the existing venv when creating the new one. After that it is typically just a matter of using pip to reinstall all dependencies from the <code>requirements.txt</code> file:
From Git Bash on Windows:
<pre class="lang-sh prettyprint-override"><code>python -m venv mynewvenv
source myvenv/Scripts/activate
pip install -r requirements.txt
</code></pre>
It can get a bit more involved if you have several local dependencies from other locally developed packages, because you may need to update local absolute paths, etc. - though if you set them up as proper Python packages, you can install from a git repo, and thus avoid this issue by having a static URL as the source.

blocks|key|843707|text|对我有效的更简单的解决方案:只需将旧虚拟环境的site-packages文件夹复制到新的虚拟环境中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|843708|entityMap^0|N|D|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|$]]

Even easier solution which worked for me: just copy the <code>site-packages</code> folder of your old virtual environment into a new one.

blocks|key|843753|text|使用Visual+Studio+Code+(vscode)，我刚刚打开了项目根目录下的./env文件夹，并进行了批量查找/替换以切换到更新后的项目名称。这解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|843754|与which+python确认|offset|length|style|CODE|843755|entityMap^0|0|1|C|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Using Visual Studio Code (vscode), I just opened the ./env folder in my project root, and did a bulk find/replace to switch to my updated project name. This resolved the issue.
Confirm with <code>which python</code>

blocks|key|628097|text|如果您使用的是conda环境，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|628098|conda+create+--name+new_name+--clone+old_name
conda+remove+--name+old_name+--all+#+or+its+alias:+`conda+env+remove+--name+old_name`|code-block|syntax|javascript|628099|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|$]]

If you are using an conda env,
<pre><code>conda create --name new_name --clone old_name
conda remove --name old_name --all # or its alias: `conda env remove --name old_name`
</code></pre>

I've created folder and initialized a virtualenv instance in it.

<pre><code>$ mkdir myproject
$ cd myproject
$ virtualenv env
</code></pre>

When I run <code>(env)$ pip freeze</code>, it shows the installed packages as it should.

Now I want to rename <code>myproject/</code> to <code>project/</code>.

<pre><code>$ mv myproject/ project/
</code></pre>

However, now when I run

<pre><code>$ . env/bin/activate
(env)$ pip freeze
</code></pre>

it says pip is not installed. How do I rename the project folder without breaking the environment?

Renaming a virtualenv folder without breaking it

Visual Studio

Windows

Python

我已经创建了一个文件夹，并在其中初始化了一个virtualenv实例。$ mkdir myproject$ cd myproject$ virtualenv env当我运行(env)$ pip freeze时，它会正常显示已安装的包。现在我想将myproject/重命名为project/。$ mv myproject/ project/但是，现在当我运行$ . env/bin/activate(e

问重命名virtualenv文件夹而不破坏它
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重命名virtualenv文件夹而不破坏它EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重命名virtualenv文件夹而不破坏它
EN