Closed jameslamb closed 4 weeks ago
One thing we would like to do is move to scikit-build-core: https://github.com/rapidsai/cucim/issues/645
Though that hasn't happened yet
We discussed some package restructuring ( https://github.com/rapidsai/cucim/issues/763 ), which would unblock scikit-build-core
Imagine things get a lot simpler to manage here if we are able to make those changes
Imagine things get a lot simpler to manage here if we are able to make those changes
"things" in general, definitely. Those look like good changes that should be made in this project.
But to be clear... the work described in those issues you linked wouldn't materially change the way this PR looks. For example, cuspatial
projects already use scikit-build-core
and have the wheels split into C++ vs. Python, and the changeset in that repo for this effort was pretty similar: https://github.com/rapidsai/cuspatial/pull/1473
/merge
Description
Contributes to https://github.com/rapidsai/build-planning/issues/108 Contributes to https://github.com/rapidsai/build-planning/issues/111
Proposes some small packaging/CI changes, matching similar changes being made across RAPIDS.
sccache
stats to CI logspip
's verbosity in wheel building scriptspy_build_{project}
andpy_rapids_build_{project}
independencies.yaml
rapids-dependency-file-generator
(v1.16.0)