skip Cython 3.2.7

[jameslamb]

Building against Cython 3.2.7 is failing, because of the issues described in cython/cython#7781

This ensures we skip that version here, which should unblock CI.

more details: #8287 (comment)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: bb6ccc9b-05bc-445d-b375-755ad5e4247b

📥 Commits

Reviewing files that changed from the base of the PR and between 91f42d1 and 56618e6.

📒 Files selected for processing (7)

• conda/environments/all_cuda-129_arch-aarch64.yaml
• conda/environments/all_cuda-129_arch-x86_64.yaml
• conda/environments/all_cuda-133_arch-aarch64.yaml
• conda/environments/all_cuda-133_arch-x86_64.yaml
• conda/recipes/cuml/recipe.yaml
• dependencies.yaml
• python/cuml/pyproject.toml

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Updated environment and build dependencies to avoid a known problematic Cython release.
  • Kept the minimum supported Cython version while excluding version 3.2.7 across supported build and test setups.

Walkthrough

All Cython version constraints are updated from >=3.2.2 to >=3.2.2,!=3.2.7 across dependencies.yaml, python/cuml/pyproject.toml, conda/recipes/cuml/recipe.yaml, and the four conda environment YAML files. A comment is added in dependencies.yaml and recipe.yaml documenting the reason for the exclusion.

Changes

Cython 3.2.7 exclusion

Layer / File(s)	Summary
Cython pin in dependencies.yaml, pyproject.toml, and conda recipe dependencies.yaml, python/cuml/pyproject.toml, conda/recipes/cuml/recipe.yaml	Adds !=3.2.7 to the Cython constraint and a comment referencing the known issue in dependencies.yaml and recipe.yaml. Both project.optional-dependencies.test and [tool.rapids-build-backend].requires entries in pyproject.toml are updated.
Generated conda environment YAMLs conda/environments/all_cuda-129_arch-aarch64.yaml, conda/environments/all_cuda-129_arch-x86_64.yaml, conda/environments/all_cuda-133_arch-aarch64.yaml, conda/environments/all_cuda-133_arch-x86_64.yaml	Each environment YAML updates the cython entry to >=3.2.2,!=3.2.7.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• rapidsai/cuml#7836: Previously set the cython>=3.2.2 lower bound in the same files this PR modifies to add the !=3.2.7 exclusion.

Suggested labels

bug

Suggested reviewers

• bdice
• gforsyth

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: excluding Cython 3.2.7.
Description check	✅ Passed	The description is directly related to the change and explains why Cython 3.2.7 is being skipped.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[jakirkham]

Thanks James! 🙏

Do we want to update these lines as well?

https://github.com/rapidsai/cuml/blob/91f42d1aeaa80d5088358be2709864cd89a3f3b1/python/cuml/README.md?plain=1#L58

https://github.com/rapidsai/cuml/blob/91f42d1aeaa80d5088358be2709864cd89a3f3b1/BUILD.md?plain=1#L22

[jameslamb]

Do we want to update these lines as well?

I really don't think it's worth another CI run. That's documentation for users / developers, information about the floor and lack of ceiling is enough.

[jcrist]

Personally, no (though I selfishly just want this merged to get on with work).

The issue seems to be some faulty upstream metadata being picked up (since 3.2.7 was marked as broken, it should be ignored in a working system). I'd leave it as is.

[jakirkham]

Understandable

Just trying to save future devs (or AI agents) running into this

This could go in a follow up PR if we deem it worthwhile

[jameslamb]

/merge