Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

ci: unit tests pin Python 3.12 while the package advertises 3.14 support

未关闭 适合新手
#8,231 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@huong8373tt-beep 已经在做这个了。

开始于 2026年10月29日。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
74/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, python
领域
ci-cd

调研方向

阅读 .github/workflows/tests.yml 和 livekit-agents/pyproject.toml,比较已测试的 Python 版本与 requires-python。检查项目依赖项和单元测试是否支持 Python 3.14,然后根据维护者的决定更新单元测试覆盖范围或缩小声明的版本范围。完成标准是:受支持的 Python 版本范围与运行时测试覆盖范围一致,并对任何例外作出说明。

由索引模型根据 Issue 内容生成。

描述

What

livekit-agents/pyproject.toml advertises requires-python = ">=3.10,<3.15", so 3.14 is a supported interpreter, but no runtime job ever runs on it:

  • .github/workflows/tests.yml pins python-version: "3.12" in all three jobs — blockguard-tests (L32), unit-tests (L56), evaluation (L83);
  • .github/workflows/ci.yml varies the interpreter only for mypy (["3.10", "3.13"]).

So the runtime test suite only ever sees 3.12. A break that is specific to 3.13/3.14 is green by construction.

Evidence that this is not theoretical

#8162 fixed exactly that class: ndarray.resize() rejects an array that is still referenced, and on 3.14 it also rejects one only held by an attribute, so VAD.update_options raised ValueError for users on that interpreter while unit-tests stayed green. The change now copies into a new array instead.

The CI gap is what let it ship — the fix is fine, the matrix is the problem. The same shape will recur for anything that depends on interpreter behaviour rather than our own logic.

Proposal

Cheapest option first, in order of preference:

  1. One 3.14 leg on unit-tests only (matrix entry or a second job), not the whole matrix — the job count stays flat and the interpreter-sensitive code paths are covered.
  2. If some dependency does not support 3.14 yet, narrow the promise instead: requires-python = ">=3.10,<3.14" plus a note, so the advertised range matches what CI actually proves.

Either way the rule worth stating is that the advertised requires-python range and the tested interpreters should not disagree without a comment saying why.

Happy to send the workflow change (option 1) if that is the direction — I did not want to add a CI job in someone else's bug-fix PR.

主要语言
Python
星标
14.6k
派生
3.9k
平均合并
2 天 6 小时
30 天内合并 PR
227

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

livekit/agents 的其他 Issue

查看 livekit/agents 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。