Skip to content

No channel isolation — the env you get depends on the user's conda config #115

Description

@LouieSlocombe

environment.yml lists conda-forge but has no nodefaults. On my machine (global config: channels: [defaults], channel_priority: flexible)

I had to force CONDA_CHANNEL_PRIORITY=strict to match CI. A user following the README verbatim gets a mixed-channel env; CI does not, because it sets channel-priority: strict and conda-remove-defaults: true.

Fix: add - nodefaults to the channels list so the file is self-contained regardless of user config.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions