Closed robertodr closed 1 year ago
Thanks for the report. Unfortunately this sort of issue is not so easily solved.
What's your motivation for using default-non-conda-source = "pip"
? Everything except numba >=0.58
should be on conda-forge
.
If you want to manage packages with pip
then you may have better luck with the recently-added skip-non-conda-lock = true
feature and running pip install
separately.
Thanks for your reply! Indeed I wanted to do something like what skip-non-conda-lock = true
would do, but on second thought, it's better to explicitly list the dependencies that aren't on conda-forge
.
As long as the dependencies are open-source licensed, it's usually not difficult to add them to conda-forge. (Generate a recipe with grayskull and submit a PR to staged-recipes.)
Checklist
What happened?
I'm using the latest version of conda-lock (2.4.1) and trying to generate a lockfile using an
environment.yml
file:and a
pyproject.toml
file:I use micromamba and run the following command:
The error I get is:
It seems this has been observed before (#221 and #253) and that #290 should have fixed it, so there must be something wrong that I'm doing.
Conda Info
Conda Config
Conda list
Additional Context
No response