-
Notifications
You must be signed in to change notification settings - Fork 66
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
remove pins on geospatial libraries, RAPIDS nightlies #722
Conversation
This reverts commit de8c29c.
🎉 looks like it's possible to solve an environment with all of RAPIDS + the newer versions of
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Smart move! I wouldn't have thought to test this repository in CI as a part of the fmt/spdlog migration.
I just added https://github.com/rapidsai/integration/actions/runs/11000951222/job/30544508462?pr=722#step:7:1138 |
🎉
|
/merge |
Contributes to rapidsai/build-planning#56
With rapidsai/cuspatial#1441, it should be possible to revert some of the workarounds introduced in #719.
Notes for Reviewers
How to test this
if this is working, we should see the following in the conda solves:
fmt >=11.0.2
spdlog >=1.14.1
We won't see
numpy >=2
yet, becausecugraph
doesn't support it yet (rapidsai/cugraph#4615).