use rapids-build-backend

[jameslamb]

Description

Contributes to rapidsai/build-planning#31
Contributes to rapidsai/dependency-file-generator#89

Proposes introducing rapids-build-backend as this project's build backend, to reduce the complexity of various CI/build scripts.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[jameslamb]

It looks like the conda-python-tests jobs are failing here, like this:

FAILED tests/basicpreds/test_intersections.py::test_one_pair - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_two_pairs - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_one_pair_with_overlap - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_two_pairs_with_intersect_and_overlap - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_one_pair_multilinestring - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_three_pairs_identical_has_ring - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead
FAILED tests/basicpreds/test_intersections.py::test_three_pairs_identical_no_ring - AssertionError: Series Expected type <class 'pandas.core.series.Series'>, found <class 'pandas.core.indexes.base.Index'> instead

(build link)

I see the same failures on #1384 (build link), so fairly confident that they're not related to the changes here.

[isVoid]

What does this 0.0.0a0 mean?

[jameslamb]

short answer

For conda, it's identical to just ==24.8.*.

For pip it means "I'm willing to accept any pre-releases of this package as well".

long answer

A version number like that is called a "pre-release".

Those are the version numbers we give to nightly RAPIDS packages.

By default, when you run pip install cuml-cu12==24.8.*, such versions will be ignored. That's so package authors can publish packages like release candidates for testing.

One option to tell pip you're open to installing such packages is to pass the --pre flag to pip install, like this:

pip install --pre 'cuml-cu12==24.8.*`

But that can have unintended consequences... --pre applies through the entire dependency tree, so running a command like that would also mean you're saying "I'm willing to pull in any pre-releases of any of cuml-cu12's dependencies as well".

Specifying a constraint like ,>=0.0.0a0 like this is a bit stricter... it tells pip "I'm willing to pull in any pre-releases of cuml-cu12 specifically, but not necessarily its dependencies".

pip install 'cuml-cu12==24.8.*,>=0.0.0a0'

There's some more discussion on this in https://peps.python.org/pep-0440/#handling-of-pre-releases

[vyasr]

We should probably update https://github.com/rapidsai/build-planning/blob/main/docs/docs/packaging.md#nightlies (and then use it as a reference).

[jameslamb]

You're totally right, I keep forgetting about those docs. I'll put up a PR there.

[bdice]

Thanks!

[jameslamb]

/merge