Repository navigation
Switch from using pip wheel to build #99
Description
The build tool is the modern approach for building packages. It is roughly equivalent to running pip wheel --no-deps. It is also much simpler and so will probably be easier to continue working with going forward. Also, as of pypa/build#655 it supports the usage of a fixed rather than arbitrary temporary directory for the build, which allows us to use sccache effectively in these jobs.
As part of this work we'll probably want to update the docs we added in #112.
Reacted by James Lamb
Metadata
Metadata
Assignees
Labels
No labels
Activity
vyasr commentedon Aug 17, 2023
Note that before we can do this we will need to get sdists properly working because (unlike
pip wheel)buildworks by first creating an sdist and then building a wheel from that.jameslamb commentedon Aug 23, 2024
I think https://github.com/rapidsai/build-planning (which didn't exist at the time that this was first written) would be a better home than
shared-workflowsfor this. Ok if I move it over there?vyasr commentedon Aug 28, 2024
Yup that is fine with me.
vyasr commentedon Aug 28, 2024
Done.
rapids-wheels-anaconda-github: support sdists (#263)
vyasr commentedon Jul 20, 2026
One of the blockers here has been resolved: pypa/build#655
vyasr commentedon Sep 4, 2026
It looks like the sdist problem is a non-issue. As long as you specify
--wheelin the build, it skips making the sdist. That means producing wheels this way is actually viable now. NVIDIA/cudf#23991 is the PoC.robertmaynard commentedon Sep 23, 2026
Closing now that we have cuml, cugraph, and cuvs siwtched over.