-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
ciRelating to Continuous Integration / GitHub ActionsRelating to Continuous Integration / GitHub ActionsdependenciesPull requests that update a dependency filePull requests that update a dependency file
Milestone
Description
Port of dsgibbons#73
We should move towards NEP 29 — Recommend Python and NumPy version support as a community policy standard
As explained in the NEP, there are several benefits of deprecating according to a predictable schedule, both for downstream users of the package and also for maintainers. The recommended drop schedule for python is:
On Dec 26, 2021 drop support for Python 3.7 (initially released on Jun 27, 2018)
On Apr 14, 2023 drop support for Python 3.8 (initially released on Oct 14, 2019)
On Apr 05, 2024 drop support for Python 3.9 (initially released on Oct 05, 2020)
On Apr 04, 2025 drop support for Python 3.10 (initially released on Oct 04, 2021)
On Apr 24, 2026 drop support for Python 3.11 (initially released on Oct 24, 2022)
It would be preferable to only drop one version per release. Suggested timeline for SHAP:
- 0.42.0 : last bugfix release for 3.7
- 0.43.0: drop support for 3.7
- 0.44.0: drop support for 3.8 (pending discussion)
Comparison with other packages (at time of writing):
- Numpy: 3.9-3.11
- Scipy: 3.9-3.11
- scikit-learn:
3.8-3.11
(3.8 will be dropped on next release)
Checklist:
- Make a prior release with a clear deprecation message
- Update
requires-python
metadata - Update PyPI classifiers
- Update CI test matrix
Metadata
Metadata
Assignees
Labels
ciRelating to Continuous Integration / GitHub ActionsRelating to Continuous Integration / GitHub ActionsdependenciesPull requests that update a dependency filePull requests that update a dependency file