Drop Python 3.10 in 2.4
Los mantenedores suelen responder en 6 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 54/100
- Tipo de issue
- Refactorización
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- python
- Área
- build-system, ci-cd
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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], andpython = ">=3.11,<3.16"in
[tool.pixi.dependencies].- Remove the
Programming Language :: Python :: 3.10classifier. [tool.ruff] target-version = "py311"and[tool.mypy] python_version = "3.11", since both
track the floor.
Test environments
- The
py310pixi feature andtest-py310environment becomepy311andtest-py311;
regeneratepixi.lock. docker-compose.yaml: the defaultPY_VERfor theappservice moves from 3.10 to 3.11 (the
Dockerfiledefault is already 3.11).
CI (.github/workflows/)
test.yaml, Linuxtestjob: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--pythondefault 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.4cannot be installed together withpandas>=2.2.2on Python 3.11: numpy 1.22.4
ships no 3.11 wheels, and pandas 2.2.2 requiresnumpy>=1.23.2on 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.pyandsrc/datajoint/codecs.pythat state 3.10. - datajoint-docs, published with the 2.4 docs:
README.mdprerequisites.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.mdrecords the 2.0 requirement and stays as is.
Packaging
- conda-forge feedstock:
python_minbecomes"3.11"with the 2.4.0 release.
Acceptance
pip install datajointon 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 checkand 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.
- Lenguaje dominante
- Python
- Estrellas
- 198
- Forks
- 103
- Merge medio
- 6 d 1 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de datajoint/datajoint-python
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1703 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1702 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1701 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
datajoint/datajoint-python#1691 ·
Los mantenedores suelen responder en 6 días
-
dependencies needs-discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
datajoint/datajoint-python#1687 ·
Los mantenedores suelen responder en 6 días
Todos los issues de datajoint/datajoint-python
Issues similares
-
cognition
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
[Suggestion]: Geonode MCP ServerAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
collabnix/awesome-mcp-lists#433 ·
Los mantenedores suelen responder en 4 días
-
CrossEntropyFilter raises on zero probabilities and single-class resultsPosiblemente ocupada @NopeCharon la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Archmonger/ServeStatic#129 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 2 días