-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Install cupy
without explicitly requesting cuda-version
now defaults to CUDA 11.8 instead of CUDA 12
#247
Comments
I suspect this is because |
Yes, I think cuda-version being a transitive dependency may be affecting this, and the cucim issue linked above. Can we add cuda-version as a dependency of cupy and not just cupy-core? |
I can do that, but to me this solver behavior is questionable (it should attempt to ensure all dependencies are updated, at least when creating a new env without any existing installation), and I'd like to confirm there's no other way to resolve this before applying any WARs. |
@leofang @bdice @jakirkham I believe I just observed something similar in |
Asking in the CF Gitter channel: https://matrix.to/#/!SOyumkgPRWoXfQYIFH:matrix.org/$170628429022aRuJZ:gitter.im?via=matrix.org&via=gitter.im&via=cadair.com |
No response to my Gitter thread, but I do find this Q&A touching on similar points:
|
I can confirm locally that
I am not sure if we want to apply any workaround. Thoughts? @bdice @jameslamb @jakirkham? |
I would apply the workaround by pinning cuda-version in cupy, and add a comment that says it helps ensure libmamba finds the right versions without unwanted upgrades. |
Thanks everyone for the discussion and Leo for the fix! 🙏 As this is a totally new package structure for It's worth noting in the RAPIDS use case, our CI runs do explicitly specify the In any event the risk in adding |
Thanks, John!
This is a bit surprising. Based on this thread I was under a different impression that the RAPIDS CIs haven't enforced it. Would be nice to check how things look like now that the fix was merged. |
Confirmed locally that the fix is working. Now both solvers behave consistently (and as intended -- newer |
Have restart CI in these (and dropped any prior workarounds) |
Have added another comment in that thread What I learned from looking at that again is the solver actually recognizes |
I'm not sure if such a package would be appreciated at conda-forge:
but it is helping us internally |
Solution to issue cannot be found in the documentation.
Issue
Either
mamba create -n my_env cupy
orconda create -n my_env cupy
now defaults to CUDA 11.8:I expect the latest CUDA to be used.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: