Closed DJohnston-Veritas closed 1 year ago
Do you have an installation of Mamba? If so, could you please try mamba --version
and see if the version of Conda it finds is also 22.9? (One hypothesis is that conda-lock is calling Mamba which uses some other version of Conda.)
@maresb I do not use Mamba. In both test cases I did a clean install of Miniconda, then create the environment from the environment.yml file. which mamba
does not find anything in the search path.
I ran into the same issue and spent some time in the debugger.
Finally I found the source of this issue which origins here since only macosx_10_9_x86_64
is considered.
If you change the line to *(f"macosx_10_{version}_x86_64" for version in range(16, 3, -1)),
it will find the packages.
If this is a valid fix I can open a PR.
Thanks a lot for putting in the debugger time to track this down, it's much appreciated!!!
I don't understand this part of the code so well. It was masterminded by @jvansanten. Perhaps he has some idea about how we should maintain this section?
Any thoughts @mariusvniekerk?
Checklist
What happened?
This environment.yml fails to resolve with conda-lock.
Conda env create
is successful on an Intel Mac.If I remove 'conda-forge', then I get an error message identical to #396
Conda Info
Conda Config
Conda list
Additional Context
Username has been redacted by replacing /Users/username with ~
Miniconda 22.11.1 is installed using pyenv, then downgraded to 22.9 (22.9 is not in the pyenv installable list). I've also tried this with the latest Miniconda installed by Homebrew and get the same error.