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
Side-effects from .condarc
: packages added from create_default_packages
#492
Comments
Thanks a lot for this bug report. This is very interesting. I'd actually argue that |
💯 This aspect of conda-lock's reproducibility is IMO really important, but not clearly enough communicated in the README or docs. The docs are really clear that conda-lock's objective is to record enough information so that a conda environment can be created twice identically (excepting packages being removed from repositories out of its control), but not so clear about the advantages of eliminating (excepting changes in repository metadata out of its control) side effects in the solving process itself. What you said above does communicate that clearly, and it feels like it would be valuable to copy it directly in to the docs :) |
Perhaps what I need for my use-case is to transform env.yaml to include channels and default packages, which should have a similar result. I could also see this as similar to environment variables however, where the spec is not complete without knowing the values. I think you could equally include default channel and package information from the .condarc in the lockfile if necessary. |
Is there anything about your use case that makes explicitly including everything in the |
It should be possible--in my use case it happens that the condarc is controlled by a build system and the dependencies are defined by the user, so that's why I care about the distinction. |
Ah, got it. You know, I wouldn't be opposed to adding |
I think that would be perfect, assuming you could provide the condarc along with a spec! I actually tried that first before submitting this issue, on a whim that it might work. |
I don't have the bandwidth to work on this. Would you like to write a |
channels
field in .condarc
doesn't seem to be respected.condarc
: packages added from create_default_packages
I'll take a look into it! |
Great! And if you see things that seem unnecessarily complicated or lacking in documentation, then if you're feeling up to it please be bold about making changes to clean things up. |
Original title:
channels
field in.condarc
doesn't seem to be respectedChecklist
What happened?
I have a
.condarc
similar to:My environment spec doesn't have
channels
.When I use conda-lock, I need to add
-c conda-forge
despite being in my condarc. I know my condarc is getting used because thecreate_default_packages
contents end up in the lockfile.Conda Info
Additional Context
No response
The text was updated successfully, but these errors were encountered: