如何预防conda env Export'从更新特定的依赖项

发布于 2025-02-08 04:25:15 字数 1104 浏览 0 评论 0原文

这是我的Environment.yml的摘录:

name: my-project
channels:
  - pytorch-nightly
  - defaults
dependencies:
  - pytorch=1.13.0.*
  - pip:
    - https://github.com/explosion/spacy-models/releases/download/nb_core_news_md-3.3.0/nb_core_news_md-3.3.0-py3-none-any.whl
prefix: ~/opt/miniconda3/envs/my-project

当我创建我的环境时(conda env create -f Environment.yml),然后将其重新输入到emovention.ymlconda env export> emovenitim.yml),文件会更改:

name: my-project
channels:
  - pytorch-nightly
  - defaults
dependencies:
  - pytorch=1.13.0.dev20220614=py3.9_0
  - pip:
    - nb-core-news-md==3.3.0
prefix: ~/opt/miniconda3/envs/my-project

然后,当我第二天重新创建环境时,康达(Conda)抱怨pytorch = 1.13。 0.DEV20220614 = PY3.9_0不存在,因为它被新的Pytorch预览(夜间)构建所取代。 dev20220614 = py3.9_0不再可用。

康达还抱怨说nb-core-news-md == 3.3.0不存在。它是通过URL直接安装到whl的。该URL已从emoverencom.yml中删除。

如何防止conda env Export更改这两个依赖性?我仍然希望康达(Conda)锁定所有其他依赖性的细节,而不是这两个依赖项。

Here's an excerpt from my environment.yml:

name: my-project
channels:
  - pytorch-nightly
  - defaults
dependencies:
  - pytorch=1.13.0.*
  - pip:
    - https://github.com/explosion/spacy-models/releases/download/nb_core_news_md-3.3.0/nb_core_news_md-3.3.0-py3-none-any.whl
prefix: ~/opt/miniconda3/envs/my-project

When I create my environment (conda env create -f environment.yml) and re-export it to environment.yml (conda env export > environment.yml), the file gets changed:

name: my-project
channels:
  - pytorch-nightly
  - defaults
dependencies:
  - pytorch=1.13.0.dev20220614=py3.9_0
  - pip:
    - nb-core-news-md==3.3.0
prefix: ~/opt/miniconda3/envs/my-project

Then, when I re-create my environment the next day, Conda complains that pytorch=1.13.0.dev20220614=py3.9_0 does not exist because it was replaced by a new PyTorch Preview (Nightly) build. dev20220614=py3.9_0 is no longer available.

Conda also complains that nb-core-news-md==3.3.0 does not exist. It was installed via a URL directly to the whl. That URL was removed from the environment.yml.

How can I prevent conda env export from changing these two dependencies? I still want Conda to lock down the specifics for all other dependencies, just not for these two.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

゛时过境迁 2025-02-15 04:25:15

我明白了为什么Pytorch删除了每日构建,但这对您拥有的工作流程有点破坏。您要要求的内容不能用Conda CLI命令表达。取而代之的是,考虑导出常规YAML,然后运行一些sed命令在重新创建环境之前替换特定要求。

I get why PyTorch is deleting daily builds, but it's kind of disruptive for the workflow you have. What you're asking for cannot be expressed with Conda CLI commands. Instead, consider exporting the regular YAML, but then run some sed commands to replace the particular requirements prior to recreating the environment.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文