-
Notifications
You must be signed in to change notification settings - Fork 104
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
Self-hosted conda-lock fails to find distutils #761
Comments
Hi @thisrod, thanks for the detailed bug report! One reason for the problems you're experiencing is the mixing of
I don't have a Windows machine, so I am unable to reproduce your procedure that involves installing. Could you please check if using one or the other leads to expected behavior? |
Hi @maresb . Thanks for the quick response! I really like the way The
The
|
Hi @thisrod, Regarding the On the conda-lock side, the defaults channel is still sneaking in to your As for why the Your workflow seems rather unconventional. Here's how I would approach what I think you're trying to do: Create a file called name: conda-locker
channels:
- conda-forge
- nodefaults
dependencies:
- python
- conda-lock
platforms:
- win-64 Now run conda env create -n bootstrap -f conda-locker.yaml
conda activate bootstrap
conda-lock -f conda-locker.yaml
conda-lock install -n conda-locker
conda deactivate
conda env remove -n bootstrap
conda activate conda-locker Note that the first command will generate the following warning that can be safely ignored:
Thanks to the As a trick for easier bootstrapping, you may want to check out micromamba. It's a drop-in replacement for
This way, once you've generated Finally, you might be interested in pixi, a next-generation tool for projects that use Conda. I think it does a really good job of alleviating these rough edges you're experiencing here. |
Hi @maresb Thanks for all that support and explanation! I suspect pixi is the right answer for what I'm doing, but I really appreciate the work you're donating to maintain conda-lock. |
Checklist
What happened?
The steps to reproduce are:
I hoped to get two identical lock files, but the last step failed with a similar symptom to #542 and #607.
The motivation for this was similar to #642, to have a Bootstrap environment with a fixed version of conda-lock.
See Additional Context for a PowerShell transcript.
Additional Context
PowerShell transcript
environment.yml
conda-lock.yml
The text was updated successfully, but these errors were encountered: