-
Notifications
You must be signed in to change notification settings - Fork 10
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
use rapids-build-backend for cugraph-gnn and cugraph-pyg #15
Comments
This was referenced Jul 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The
cugraph-gnn
andcugraph-pyg
packgaes currently usesetuptools
as their build backends.cugraph-gnn/python/cugraph-dgl/pyproject.toml
Line 9 in 666d114
cugraph-gnn/python/cugraph-pyg/pyproject.toml
Lines 3 to 8 in 666d114
They should use `rapids-build-backend.
Benefits of this work
Would make these projects' build systems consistent with the rest of RAPIDS.
Would reduce the need for complexity like this in build scripts:
cugraph-gnn/ci/build_wheel.sh
Lines 28 to 43 in 666d114
Acceptance Criteria
cugraph-gnn
andcugrpah-pyg
userapids-build-backend
as their build backend.pre-commit-config.yaml
includes theverify-alpha-spec
hookApproach
Follow the work in these examples:
cugraph
changes: Use rapids-build-backend cugraph#4393setuptools
example: use rapids-build-backend dask-cuda#1343And other things described in rapidsai/build-planning#31.
Notes
N/A
The text was updated successfully, but these errors were encountered: