Repository navigation
Follow SPEC 0 instead of NEP 29 - #578
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #578 +/- ##
=======================================
Coverage 79.71% 79.71%
=======================================
Files 70 70
Lines 8315 8315
Branches 1506 1506
=======================================
Hits 6628 6628
Misses 1198 1198
Partials 489 489 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
dilpath
approved these changes
Nov 16, 2026
| We follow `SPEC 0 <https://scientific-python.org/specs/spec-0000/>`_ | ||
| for the minimum supported versions of Python and core dependencies | ||
| (NumPy, SciPy, Matplotlib, pandas, ...), | ||
| but may keep supporting a Python version until NumPy drops it. |
Member
There was a problem hiding this comment.
What does this mean? The note on NEP 29 says that numpy also follows SPEC 0?
Fine to keep python 3.12 support for now though
Member
Author
There was a problem hiding this comment.
That's +/- correct, but today's numpy release still supports 3.12.
Switch the minimum-version policy for Python and core dependencies from NEP 29 to SPEC 0. Python versions may be supported until NumPy drops them, so Python 3.12 is kept for now. Raise minimum versions accordingly: `numpy>=2.2`, `matplotlib>=3.10`, `scipy>=1.15`, and `ipython>=8.30` in the `doc` group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dweindl
enabled auto-merge (squash)
November 16, 2026 18:12
dweindl
disabled auto-merge
November 16, 2026 18:12
dweindl
enabled auto-merge (squash)
November 16, 2026 18:21
dweindl
disabled auto-merge
November 16, 2026 18:54
dweindl
enabled auto-merge
November 16, 2026 18:54
dweindl
added a commit
to dweindl/libpetab-python
that referenced
this pull request
Nov 17, 2026
…v#600) Every pull request added its changelog entry at the same place in `CHANGELOG.md`, so concurrent pull requests conflicted with each other. Now, each pull request adds its changelog entry as a separate file `changelog.d/+<name>.<type>.md` (see `changelog.d/README.md`). At release time, `towncrier build --version X.Y.Z` collects them into `CHANGELOG.md` and removes the fragments. The template in `changelog.d/template.md.j2` reproduces the existing format (`**Fixes**` etc., `* ` bullets with 2-space continuation lines). Entries are sorted alphabetically within each category; grouping them (e.g., by PEtab version or module) is done when compiling the release notes. The configuration is in `pyproject.toml`, and towncrier is added to the `test` dependency group. The release process in `doc/development.rst` is updated accordingly. Entries now link to the pull request only, without "by @user"; contributors can be credited in the release notes. The unreleased 0.11.0 entry (PEtab-dev#578) is moved to `changelog.d/`, and entries are added for PEtab-dev#583, PEtab-dev#584, PEtab-dev#588, PEtab-dev#590, PEtab-dev#592 and PEtab-dev#595, which did not add one. The behaviour changes from PEtab-dev#584 (top-level Boolean expressions are returned as `Piecewise`) and PEtab-dev#592 (stricter `PySBModel.pattern_from_string`) are listed as breaking changes. Open pull requests that edit `CHANGELOG.md` will need to move their entry to a fragment file. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Switch the minimum-version policy for Python and core dependencies from NEP 29 (superseded) to SPEC 0. A Python version may be supported as long as current NumPy releases support it, so Python 3.12 is kept for now (SPEC 0 would drop it this quarter; NumPy 2.5 and SciPy 1.18 still support it).
Raise minimum versions accordingly:
numpy>=2.2,matplotlib>=3.10,scipy>=1.15, andipython>=8.30in thedocgroup.pandas>=2.3already matches.🤖 Generated with Claude Code