You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pyproject.toml classifiers stop at Python 3.12 but CI tests 3.13 #838
PyPI trove classifiers in pyproject.toml list Python 3.8–3.12, but CI in .github/workflows/main.yml tests 3.9–3.13. This misinforms PyPI users on 3.13 and lists 3.8 as supported despite it being dropped from CI.
Steps
Read pyproject.toml lines 12–18 at master.
Read .github/workflows/main.yml matrix line.
Expected
Classifiers match the CI test matrix, and requires-python reflects the actual minimum.
Actual
pyproject.toml:
requires-python = '>=3.8'
...
'Programming Language :: Python :: 3.8',
'Programming Language :: Python :: 3.9',
'Programming Language :: Python :: 3.10',
'Programming Language :: Python :: 3.11',
'Programming Language :: Python :: 3.12',
The supported-version contract should be decided first: if Python 3.8 is genuinely supported, restore it to CI; otherwise raise requires-python and remove the classifier in the same release. Adding 3.13 only to classifiers without testing package build, imports, and the suite would still be misleading. A packaging check can compare the CI matrix, requires-python, and trove classifiers to prevent future drift.
Activity
hiSandog commentedon Jul 18, 2026
The supported-version contract should be decided first: if Python 3.8 is genuinely supported, restore it to CI; otherwise raise
requires-pythonand remove the classifier in the same release. Adding 3.13 only to classifiers without testing package build, imports, and the suite would still be misleading. A packaging check can compare the CI matrix,requires-python, and trove classifiers to prevent future drift.