Drop Python 3.10 in 2.4
維護者通常 6 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 54/100
- Issue 類型
- 重構
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- python
- 領域
- build-system, ci-cd
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 主要語言
- Python
- 星號
- 198
- 分支
- 103
- 平均合併
- 6 天 1 小時
- 30 天內合併 PR
- 10
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
datajoint/datajoint-python 的其他 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
datajoint/datajoint-python#1703 ·
維護者通常 6 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
datajoint/datajoint-python#1702 ·
維護者通常 6 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
datajoint/datajoint-python#1701 ·
維護者通常 6 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 74/100
datajoint/datajoint-python#1691 ·
維護者通常 6 天內回覆
-
dependencies needs-discussion
難度 2/5 1-3 小時 新手友好度 68/100
datajoint/datajoint-python#1687 ·
維護者通常 6 天內回覆
查看 datajoint/datajoint-python 的全部 Issue
相似的 Issue
-
needs-triage
難度 1/5 1-3 小時 新手友好度 85/100
gke-labs/kube-agents#6620 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 75/100
open-webui/open-webui#34719 · 2 則留言 ·
維護者通常 1 天內回覆
-
cognition
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
One non-object JSON record makes the session catalog exit可能已有人在做 @he-yufeng 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 78/100
collabnix/awesome-mcp-lists#433 ·
維護者通常 4 天內回覆