Drop Python 3.10 in 2.4

Ouverte
#1,694 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
54/100
Type d'issue
Refactorisation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
python
Domaine
build-system, ci-cd

Piste de recherche

Start with pyproject.toml (requires-python, the 3.10 classifier, [tool.ruff] and [tool.mypy] targets) and the pixi manifest, then rename the py310 feature/test-py310 environment and regenerate pixi.lock. Next update .github/workflows/test.yaml and post_draft_release_published.yaml matrices, and docker-compose.yaml's PY_VER. The fiddly part is the dependency floor: run minimum_requirements.py --python 3.11 and confirm the numpy bump to 1.23.2 plus other minimums resolve. Finish with CONTRIBUTING.md and the two module docstrings; docs live in the separate datajoint-docs repo. Done means the acceptance list holds on both the 2.4 and 2.3 lines.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement

Why

Python 3.10 reached end of life in October 2026 and no longer receives security fixes. DataJoint
2.4 is the next minor release, and raising the floor is a breaking change, so it belongs there
rather than in a 2.3.x patch. The plan was set in
datajoint/datajoint-python#1569: raise
the ceiling to 3.15 in 2.3.5 (done), drop 3.10 in 2.4.

The 2.3 line keeps Python 3.10. Users who must stay on 3.10 can pin datajoint<2.4; patch
releases on the 2.3 line keep requires-python = ">=3.10,<3.16" and the 3.10 CI legs.

What changes

Package metadata (pyproject.toml)

  • requires-python = ">=3.11,<3.16" in [project], and python = ">=3.11,<3.16" in
    [tool.pixi.dependencies].
  • Remove the Programming Language :: Python :: 3.10 classifier.
  • [tool.ruff] target-version = "py311" and [tool.mypy] python_version = "3.11", since both
    track the floor.

Test environments

  • The py310 pixi feature and test-py310 environment become py311 and test-py311;
    regenerate pixi.lock.
  • docker-compose.yaml: the default PY_VER for the app service moves from 3.10 to 3.11 (the
    Dockerfile default is already 3.11).

CI (.github/workflows/)

  • test.yaml, Linux test job: environment: [test-py311, test-py314, test-py315].
  • test.yaml, unit-tests-windows: python-version: ["3.11", "3.14", "3.15"].
  • test.yaml, minimum-dependency-versions job: run on Python 3.11 and call
    minimum_requirements.py --python 3.11; the script's --python default moves to 3.11.
  • post_draft_release_published.yaml: build the release on 3.11 (the oldest supported version).
  • Comments that restate the supported range move to >=3.11,<3.16.

Dependency minimums

  • numpy>=1.22.4 cannot be installed together with pandas>=2.2.2 on Python 3.11: numpy 1.22.4
    ships no 3.11 wheels, and pandas 2.2.2 requires numpy>=1.23.2 on 3.11. Raise the numpy minimum
    to 1.23.2 so the minimum-dependency-versions job can resolve on the new floor. Check the other
    minimums for 3.11 wheels at the same time.

Docs and text that state supported versions

  • CONTRIBUTING.md: "Python 3.10+" becomes "Python 3.11+".
  • Module docstrings in src/datajoint/types.py and src/datajoint/codecs.py that state 3.10.
  • datajoint-docs, published with the 2.4 docs:
    • README.md prerequisites.
    • src/how-to/installation.md: the requirements list, and the CI coverage notes, which name the
      tested range (also out of date about 3.15).
    • src/reference/specs/type-system.md: the codec auto-registration note ("Requires Python
      3.10+").
    • The 2.4 release notes: state the new floor and that the 2.3 line keeps 3.10.
    • src/how-to/migrate-to-v20.md records the 2.0 requirement and stays as is.

Packaging

  • conda-forge feedstock: python_min becomes "3.11" with the 2.4.0 release.

Acceptance

  • pip install datajoint on Python 3.10 resolves to the newest 2.3.x release; 2.4 declares
    requires-python = ">=3.11,<3.16" and carries no 3.10 classifier.
  • No CI job, pixi environment, or release workflow installs or tests Python 3.10 on the 2.4 line;
    the Linux and Windows matrices cover 3.11, 3.14 and 3.15.
  • The minimum-dependency-versions job passes on Python 3.11.
  • ruff check and the pre-commit hooks pass with the 3.11 targets.
  • No file in datajoint-python or datajoint-docs states 3.10 as the supported floor for 2.4.
  • The 2.3 line still declares and tests Python 3.10.
Langage dominant
Python
Étoiles
198
Forks
103
Merge moyen
6 j 1 h
PR mergées (30 j)
10

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de datajoint/datajoint-python

Toutes les issues de datajoint/datajoint-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.