-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support channel prefix in environment.yaml #7202
Comments
Oh, xref #2800, which was closed. That issue consisted of multiple things, only one of which was supporting the |
I think this was probably fixed with #7178 |
Oh cool. Is that change in conda canary? If so I can try it out and report back. |
Yeah, it is. In 4.6.0a1. |
Def appreciate the testing support! |
Just tried it out, and things seemed to work perfectly. Thanks! |
Can we put this in the documentation for 'Managing Environments' please |
Is this behavior/functionality documented anywhere? If so, where? |
@akapocsi Nowhere it seems. I didn't even know this feature existed (not sure if it's working yet). |
I had some correspondence, that I can't find from someone associated with anaconda, which said words to the effect that "the feature is supported but not documented" |
the only documentation I've found so far: https://stackoverflow.com/a/47887331/4139249 |
Hi @kalefranz how can I specify multiple channels for a pkg, e.g. |
@danielyan86129 please open a new issue |
I couldn't find anywhere whether the channel would also apply to the dependencies of the package prefixed with the channel, or if it only applies to the package itself (and its dependencies would be searched in the default channels). |
I'm submitting a...
It'd be nice if
conda env create
supported thechannel::package
syntax in thedependencies
list.Current Behavior
Unclear, but I think that any channels detected as a prefix are pre-pended to the list of channels, and the install proceeds.
Steps to Reproduce
Given this
environment.yaml
file,Expected Behavior
I'd expect python and flask to come from the highest priority channel (defaults), and requests to come from conda-forge. It looks like conda-forge was added as the highest priority. I'd further expect that the prefix applies only to requests (and its dependencies?). If I listed another dependency with no channel prefix that's found in conda-forge but not requests, it should error (I think).
Environment Information
`conda info`
`conda config --show-sources`
`conda list --show-channel-urls`
The text was updated successfully, but these errors were encountered: