Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

environment.yml: channel-name::package-name syntax has global effect #9993

Closed
w-hc opened this issue Jun 9, 2020 · 3 comments
Closed

environment.yml: channel-name::package-name syntax has global effect #9993

w-hc opened this issue Jun 9, 2020 · 3 comments
Labels
locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::bug describes erroneous operation, use severity::* to classify the type

Comments

@w-hc
Copy link

w-hc commented Jun 9, 2020

conda version 4.8.3

When I create the following environment.yml

name: temp
channels:
  - defaults
dependencies:
  - python=3
  - numpy
  - conda-forge::av
  - jupyterlab=2.1.4

I expect that conda-forge::av would only introduce conda-forge channel to that single package. Other dependencies should not be able to access anything from conda-forge.
Currently jupyterlab=2.1.4 is not available in the default channel, and so I expect the installation to fail.
In reality however conda would go ahead to fetch jupyterlab=2.1.4 from conda-forge, without notifying me what happened.

I also tried this

name: temp
channels:
  - defaults
dependencies:
  - python=3
  - numpy
  - jupyterlab=2.1.4

In this case, conda-forge does not appear anywhere, and the installation fails as it should.

The desired behavior should be to isolate the effect of the channel specifier to the single line, not exposing it globally.

@w-hc w-hc changed the title environment.yml: channel-name::package-name has global effect environment.yml: channel-name::package-name syntax has global effect Jun 9, 2020
@w-hc
Copy link
Author

w-hc commented Jun 9, 2020

#2800, #7202 both refer to this problem. However it seems that isolated per dependency channel is still not there.

@angloyna angloyna added the type::bug describes erroneous operation, use severity::* to classify the type label Jul 22, 2020
@angloyna
Copy link
Contributor

I think we've since updated our jupyterlab on the defaults channel to include v2.1.4, but I was able to reproduce this by adding a different package from conda-forge which doesn't exist in defaults.

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Jul 20, 2022
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Aug 19, 2022
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 19, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::bug describes erroneous operation, use severity::* to classify the type
Projects
None yet
Development

No branches or pull requests

2 participants