Skip to content

pyproject.toml classifiers stop at Python 3.12 but CI tests 3.13 #838

Closed

Description

@chirag127

Problem

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

  1. Read pyproject.toml lines 12–18 at master.
  2. 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',

.github/workflows/main.yml:

python-version: ['3.9', '3.10', '3.11', '3.12', '3.13']

Environment

rope master @ a32584f (1.14.0), file pyproject.toml lines 6, 12–18; .github/workflows/main.yml matrix.

Thanks for maintaining python-rope/rope!

Activity

  1. hiSandog commented on Jul 18, 2026

    @hiSandog

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions