conda create --clone v.s.直接复制环境 [英] conda create --clone v.s. copying the environment directly

问题描述

https://docs.conda.io/projects/conda/zh-CN/latest/user-guide/tasks/manage-environments.html

我了解

您可以通过创建以下环境的副本来精确复制环境:它:

You can make an exact copy of an environment by creating a clone of it:

conda create --name myclone --clone myenv

其中 myenv 是现有环境.

推荐答案

Conda维护硬链接以减少物理磁盘使用量.普通复制只会简单地进行物理复制，从而不必要地浪费了一堆空间.

Conda maintains hardlinks to reduce physical disk usage. Normal copying will simply make physical duplicates, wasting a bunch of space unnecessarily.

另一个可能引起更多问题的问题是运行安装脚本的软件包的问题.如果这些脚本的结果最初导致使用绝对路径的设置，则复制将导致以隐秘的方式耦合到原始环境.这可能会导致原始环境中的更改隐含地影响复制的环境.

Another potentially more problematic issue is that of packages that run installation scripts. If the results of those scripts originally led to settings that use absolute paths, then copying would result in coupling to the original environment in a cryptic way. This could lead to changes in the original environment implicitly affecting the copied one.

这篇关于conda create --clone v.s.直接复制环境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！