Skip to content

Warn on Python 3.10 that 0.15 will not support it - #128

Merged
ml31415 merged 1 commit into
masterfrom
python-eol-notice
Oct 16, 2026
Merged

ml31415 merged 1 commit into
masterfrom
python-eol-notice

Conversation

@ml31415

@ml31415 ml31415 commented Oct 16, 2026

Copy link
Copy Markdown
Owner

import numpy_groupies on Python 3.10 now says out loud what the classifiers only implied: the 0.14 releases are the last ones that support this interpreter, 0.15 will require 3.11.

The floor is the one constant _next_release_floor = (3, 11) in numpy_groupies/__init__.py, and pyproject.toml carries a comment on requires-python about raising it - dropping 3.10 for real will be two edits.

The check takes the interpreter version as an argument instead of reading sys.version_info itself, which is what makes it testable in both directions on any interpreter: (3, 11) up to (3, 15) must stay silent under an "error" filter, (3, 9), (3, 10) and (3, 10, 12) must warn, and the message must name the required version and the running one.

Verified on a real 3.10.21 interpreter:

$ python -W default::DeprecationWarning -c "import numpy_groupies"
__init__.py:120: DeprecationWarning: numpy-groupies will require Python 3.11 or newer from version 0.15, and the 0.14 releases are the last to support this interpreter (3.10.21).

DeprecationWarning is Python's own choice for an interpreter that is about to be dropped, and it follows the usual rule of being hidden unless asked for - it shows up under -W default, under -X dev, and in the warnings summary of a pytest session, which is where the 3.10 CI job will now carry it.

@ml31415
ml31415 merged commit 8b5e99f into master Oct 16, 2026
18 of 24 checks passed
@ml31415
ml31415 deleted the python-eol-notice branch October 20, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant