Skip to content

Require cunumpy>=0.7.2 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max-models merged 1 commit into from
Oct 27, 2026
Merged

Require cunumpy>=0.7.2 #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
`kernels/_build.py`, `kernels/_metal.py` and `kernels/compile.py` are gone, and the build
cache is still `MPIFIELD_KERNEL_CACHE`. `shared_memory_fits` is
`xp.cuda.shared_memory_fits`; the catalog no longer exports it.
- Needs `cunumpy>=0.7.2`, the first release with `KernelPackage` (was `>=0.7`, with which
`import mpifield` failed on cunumpy 0.7.0 and 0.7.1).

### Added

Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ classifiers = [
# PyPI rejects direct references (name @ git+...), so only version ranges go here; the
# max-models packages come from their devel branches through [tool.uv.sources]
dependencies = [
"cunumpy>=0.7",
"cunumpy>=0.7.2",
# MPI only under an MPI launcher (mpirun, srun); a serial stand-in for mpi4py otherwise
"maybempi>=0.1.2",
"mpiarray>=0.2.1",
Expand Down
Loading