Different solver behavior based on how build string in requirement is spelled #604
Open
2 tasks done
Labels
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
Trying to create an environment on an x86_64 macOS system, I've found that the behavior of
conda install
appears to differ based on how I spell the Python requirement.I'd expected these to be different spellings that translate to identical representations for the solver, and therefore to not affect solves at all.
Conda Info
output of 'conda info' (click me)
Conda Config
Conda list
output of 'conda list' (click me)
Additional Context
Reproducible Example
This fails:
conda create \ --override-channels \ -c conda-forge \ -c nodefaults \ -y \ --dry-run \ -n delete-me \ --file ./.ci/conda-envs/ci-core.txt \ 'python=3.9=*_cp*'
full logs (click me)
The following succeeds. Notice that the only difference is the spelling of the
python
requirement.full logs (click me)
I do see that the two
MatchSpec
objects do not compare equal, though I'm not sure where the differences are.The text was updated successfully, but these errors were encountered: