cuda-python / cuda_python

NVIDIA/cuda-python/cuda_python/AGENTS.md

This file describes cuda_python, the metapackage layer in the cuda-python monorepo. - cudapython is primarily packaging and documentation glue. - It does not host substantial runtime APIs like cudacore, cudabindings, or cudapathfinder. - pyproject.toml: project metadata and dynamic dependency declaration. - setup.py: dynamic dependency pinning logic for matching cuda-bindings versions (release vs pre-release behavior). - docs/: top-level docs build/aggregation scripts. - Keep this package lightweight; prefer implementing runtime features in the component packages rather than here. - Be careful when…

AGENTS.md3.4k starsChanged 48 days ago

View on GitHub Discuss

This file describes `cuda_python`, the metapackage layer in the `cuda-python`
monorepo.

## Scope

- `cuda_python` is primarily packaging and documentation glue.
- It does not host substantial runtime APIs like `cuda_core`,
  `cuda_bindings`, or `cuda_pathfinder`.

## Main files to edit

- `pyproject.toml`: project metadata and dynamic dependency declaration.
- `setup.py`: dynamic dependency pinning logic for matching `cuda-bindings`
  versions (release vs pre-release behavior).
- `docs/`: top-level docs build/aggregation scripts.

## Editing guidance

- Keep this package lightweight; prefer implementing runtime features in the
  component packages rather than here.
- Be careful when changing dependency/version logic in `setup.py`; preserve
  compatibility between metapackage versioning and subpackage constraints.
- If you update docs structure, ensure `docs/build_all_docs.sh` still collects
  docs from `cuda_python`, `cuda_bindings`, `cuda_core`, and `cuda_pathfinder`.

Discussion

Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.

Posts are public.Sign in to post

No one has posted yet. Be the first.