NVIDIA / NVIDIA/cuda-python

Drive PR #2266 (Migrating cuda-python sample codes from cuda-samples repository and Testing) across the finish line

Open
#2,866 0 comments 0 reactions 1 assignee View on GitHub

@lijinf2 is already working on this.

Since Sep 15, 2026.

triage
Dominant language
Cython
Stars
3.4k
Forks
329
Avg merge
1d 23h
Merged PRs (30d)
116

Description

Context

PR #2266 — Migrating cuda-python samples from cuda-samples repository and Testing — has been open since June 25, 2026 and represents significant work (40 commits, +38863/-20564 across 247 files) to establish cuda-python as the canonical source of truth for CUDA samples, which will then be synced back to the cuda-samples repo on each release.

Current Status

  • ✅ CI is green (as of Sep 9, 2026)
  • ✅ Approved by @rparolin
  • ✅ All existing examples from cuda_bindings/examples and cuda_core/examples have been migrated into samples/cuda_bindings and samples/cuda_core
  • ✅ Samples are integrated into the main cuda.core and cuda.bindings test suites (no longer a separate suite)
  • ✅ Platform-specific waivers added (WSL, Windows TCC, headless OpenGL, managed memory, etc.)
  • ⏳ Awaiting final review. @leofang

Remaining Blockers

  1. Review from @leofang — the last requested reviewer; PR cannot merge until their review is complete or dismissed
  2. Documentation checklist — the "documentation is up to date" checklist item in the PR is unchecked; needs clarification whether it's intentional follow-up work or needs to be addressed now
  3. mdboom's "changes requested" status — needs to be resolved/dismissed once all concerns are confirmed addressed

Ask

Please prioritize reviewing and merging PR #2266. The PR is now in a good state with green CI. If it's too large to review in one pass, consider whether splitting into smaller follow-up PRs (as suggested by @lijinf2) is feasible to accelerate the final mile.

Ref: https://github.com/NVIDIA/cuda-python/pull/2266
Milestone: cuda.bindings 13.4.0 & 12.9.8
Labels: P0, cuda.core, cuda.bindings, example

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.