We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Cross-linking related issue from conda-forge/scikit-learn-feedstock#271)
There seems to be no way to have these 2 packages installed together with the current conda builds for pytorch:
scikit-learn >=1.4 (from the conda-forge channel) pytorch >=2.3 (from pytorch channel)
Test command:
mamba create --strict-channel-priority --override-channels -c pytorch -c conda-forge -n test --dry-run 'scikit-learn>=1.4' 'pytorch>=2.3'
The problem seems related to this package's very restrictive pinning on llvm-openmp<16 and the way this dependency is treated on conda-forge (c.f.: conda-forge/scikit-learn-feedstock#265, conda-forge/openmp-feedstock#126).
llvm-openmp<16
The offending line seems to come from: https://github.com/pytorch/builder/blob/main/conda/pytorch-nightly/meta.yaml#L49
I wonder if the issue is still present with versions 17 or 18 of LLVM, and if one could update this pin to allow for a more inclusive software stack.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
(Cross-linking related issue from conda-forge/scikit-learn-feedstock#271)
There seems to be no way to have these 2 packages installed together with the current conda builds for pytorch:
scikit-learn >=1.4 (from the conda-forge channel)
pytorch >=2.3 (from pytorch channel)
Test command:
The problem seems related to this package's very restrictive pinning on
llvm-openmp<16
and the way this dependency is treated on conda-forge (c.f.: conda-forge/scikit-learn-feedstock#265, conda-forge/openmp-feedstock#126).The offending line seems to come from: https://github.com/pytorch/builder/blob/main/conda/pytorch-nightly/meta.yaml#L49
I wonder if the issue is still present with versions 17 or 18 of LLVM, and if one could update this pin to allow for a more inclusive software stack.
The text was updated successfully, but these errors were encountered: