allow pandas patch version to float in cudf-pandas unit tests

[jameslamb]

Description

#16745 added support for Python 3.12 in this project.

When that was merged, nightly unit-tests-cudf-pandas jobs on Python 3.12 started failing, with errors from compiling pandas: (build link)

That's only happening because we're running pip install pandas==2.1 in those jobs, which matches exactly pandas==2.1.0, which does not have Python 3.12 wheels on PyPI (https://pypi.org/project/pandas/2.1.0/#files).

Collecting pandas==2.1
  Downloading pandas-2.1.0.tar.gz (4.3 MB)

pandas==2.1.1 DOES have Python 3.12 wheels on PyPI (https://pypi.org/project/pandas/2.1.1/#files).

To fix those jobs, this proposes allowing the patch version of pandas installed in those CI jobs to float:

• before: pip install pandas==2.1
• after: pip install pandas==2.1.*

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]

version here is always of the form {major}.{minor}, populated by this script that reads dependencies.yaml:

cudf/ci/cudf_pandas_scripts/fetch_pandas_versions.py

Line 15 in 7018a33

matching_minors = sorted(set(".".join((str(v.major), str(v.minor))) for v in matching_versions), key=Version)

[jameslamb]

pip devcontainers builds are failing because dask-cuda (unsuffixed) is ending up in the install list.

ERROR: No matching distribution found for dask-cuda==24.10.*,>=0.0.0a0

(build link)

Looking into it.

I forgot, dask-cuda should be unsuffixed: https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/dask-cuda/. Maybe this was just a network error, I'll try restarting it.

[jameslamb]

/merge