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

Extend ASYNC401 to other forms

未关闭
#475 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
tooling

调研方向

Start by locating the ASYNC401 implementation and its tests in the repository. Compare the rule's handling of the listed pytest.raises, pytest.RaisesExc, pytest.RaisesGroup, and pytest.mark.xfail forms, then update coverage so the equivalent ExceptionGroup usages are reported as described.

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

描述

I was looking at implementing ASYNC401 in Ruff and noticed that there are a couple forms that the rule here doesn't capture but arguably should.

  • pytest.mark.xfail(raises=ExceptionGroup) could be pytest.mark.xfail(raises=pytest.RaisesGroup(...))
  • pytest.RaisesGroup(ExceptionGroup) could be pytest.RaisesGroup(pytest.RaisesGroup(...))
  • pytest.raises(ExceptionGroup[Exception]) and pytest.RaisesExc(ExceptionGroup) are ignored even though they are equivalent to pytest.raises(ExceptionGroup)

Would there be interest in updating the rule to report on the usages above as well?

主要语言
Python
星标
26
派生
10
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

python-trio/flake8-async 的其他 Issue

查看 python-trio/flake8-async 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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