Repository navigation
build: relax dependency bounds and support Python 3.10–3.15 - #63
Merged
Merged
Conversation
Every lower bound is now verified by running the test suite with `uv --resolution lowest-direct` instead of being guessed. - declare requires-python >=3.10 (was missing; numpy>=2.4.4 forced 3.11+) - numpy >=2.4.4 -> >=1.22; fall back to np.trapz on numpy 1.x - declare torch >=2.3 (imported directly; <2.3 breaks with numpy 2) - mrzerocore >=0.4.7 -> >=1.0.0 (older lacks Pulse.grad/freq_offset/duration), >=1.4.0 on Python 3.10 (typing.Self) and 3.15 (h5py has no wheels) - pypulseq >=1.4 -> >=1.5 (to_mr0 fails on 1.4.x) - upgrade locked mrzerocore to 1.4.0, which drops ismrmrd/h5py/scikit-image - CI: lowest-direct on 3.10 and 3.11, latest on 3.15 - README: document supported versions; drop stale "no runtime deps" and PyPulseq 1.4 claims Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes pulseq-zero easier to install alongside other packages. The supported Python range is widened, and every dependency floor is the lowest version that the test suite actually passes on.
Dependency changes
>=3.10>=2.4.4>=1.22np.trapezoidnow falls back tonp.trapzon numpy 1.x>=2.3autograd.Functions need ≥2.0, and torch <2.3 fails with "Numpy is not available" when installed alongside numpy 2>=0.4.7>=1.0.0(>=1.4.0on 3.10 and 3.15)Pulse.grad/freq_offset/duration. 1.0.2–1.3.0 fail to import on 3.10 (typing.Self). Before 1.4, mrzerocore pulled in h5py, which has no 3.15 wheels>=1.4>=1.5to_mr0()fails on 1.4.x, so the README's 1.4 claim was wronguv.locknow uses mrzerocore 1.4.0, which no longer pulls in ismrmrd, h5py, scikit-image or torchkbnufft by default. The demos don't use any of them.Testing
The full suite (67 tests) and the adapter completeness check were run in fresh uv venvs:
Combinations that fail, which is why the bounds are set where they are: torch 1.13, torch 2.0–2.2 with numpy 2, mrzerocore 0.4.x, pypulseq 1.4.x.
CI now runs the oldest allowed dependency versions on 3.10 and 3.11 (
uv --resolution lowest-direct) and the newest on 3.15, so a bound that becomes too low makes CI fail. This workflow has not run on GitHub yet, so please check the first run.The second commit bumps the version to 1.2.0 and adds the changelog entry.
🤖 Generated with Claude Code