Python version policy: test all supported versions and update once a year
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
调研方向
Start with HOWTOCONTRIBUTE.md and doc/ARCHITECTURE.md to define the yearly Python support policy, then inspect the CI workflow matrix and the README, Dockerfile, .devcontainer/devcontainer.json, and Update_Examples_Gallery.yml version settings. Check dependency support for Python 3.11–3.15 and document any version left out of CI. Done when the policy is documented, the recommended version is applied to the listed files, and CI passes across the supported matrix.
由索引模型根据 Issue 内容生成。
描述
Part of #131.
Problem
CI tests only Python 3.13, and the README, the Dockerfile and the gallery workflow all use 3.13. There is no rule for when to move to a newer version or which versions are supported.
- Users run different versions (for example 3.10 on Ubuntu 22.04 and 3.12 on Ubuntu 24.04), but only one is tested
- The library release (#172) needs to declare
requires-python - The Dockerfile is pinned to
python:3.13.0, so it doesn't get the bug and security fixes of later 3.13.x releases
Expected change
- Write the policy in
HOWTOCONTRIBUTE.md(and refer to it fromdoc/ARCHITECTURE.md):- Supported versions: every Python version that hasn't reached its end of life. CI tests all of them
- Recommended version: the newest version minus one. The README, the Dockerfile, the devcontainer and the gallery workflow use it. The newest version is not recommended right after its release, because the dependencies (numpy, scipy, matplotlib, casadi, do-mpc) may not have wheels for it yet
- Yearly review in December or January, after the October release of Python: add the new version to CI once the dependencies support it, move the recommended version up by one, and drop versions that reached their end of life
- Apply it for this year:
- CI matrix (Linux, macOS, Windows): 3.11 to 3.15. A version that a dependency doesn't support yet stays out of the matrix, with a comment saying why
- Recommended version: 3.14 in the README,
Dockerfile(python:3.14, without a patch number),.devcontainer/devcontainer.jsonandUpdate_Examples_Gallery.yml
Done when
- The policy is in
HOWTOCONTRIBUTE.md - CI passes on every supported version in the matrix
- The README, the Dockerfile, the devcontainer and the gallery workflow use the recommended version
Related: #172 (requires-python of the package), #165 (book versions follow the same yearly cycle).
- 主要语言
- Python
- 星标
- 1.9k
- 派生
- 313
- 平均合并
- 18 小时 46 分钟
- 30 天内合并 PR
- 35
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ShisatoYano/AutonomousVehicleControlBeginnersGuide 的其他 Issue
-
announce documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 76/100
ShisatoYano/AutonomousVehicleControlBeginnersGuide#199 ·
维护者通常 1 天内回复
-
good first issue refactoring
难度 2/5 1-3 小时 新手友好度 82/100
ShisatoYano/AutonomousVehicleControlBeginnersGuide#129 · 1 条评论 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 78/100
ShisatoYano/AutonomousVehicleControlBeginnersGuide#99 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 82/100
ShisatoYano/AutonomousVehicleControlBeginnersGuide#98 ·
维护者通常 1 天内回复
-
documentation
难度 4/5 3-5 天 新手友好度 38/100
ShisatoYano/AutonomousVehicleControlBeginnersGuide#221 ·
维护者通常 1 天内回复
查看 ShisatoYano/AutonomousVehicleControlBeginnersGuide 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 79/100
vllm-project/vllm-omni#10051 · 1 条评论 ·
维护者通常 1 天内回复
-
Bug Testing
难度 2/5 1-3 小时 新手友好度 78/100
SCIInstitute/SCIRun#2931 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 5 天内回复
-
author-page correction
难度 2/5 1-3 小时 新手友好度 64/100
acl-org/acl-anthology#10827 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 91/100
marimo-team/marimo#11768 ·
维护者通常 1 天内回复