-W option cannot use non-standard categories

未关闭
#66,733 10 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
cli

调研方向

Start with the issue title and the linked bugs.python.org issue 22543, focusing on how Python's -W option handles warning categories. The payload names no source file, test, or entry point, so locate the option's implementation and existing warning-filter tests first. Done means non-standard warning categories can be used with -W and the behavior is covered by tests.

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

描述

3.7 (EOL) 3.9 (EOL) stdlib type-bug
BPO 22543
Nosy @pitrou, @Bluehorn, @gerritholl, @mitya57, @mmerickel, @remram44, @kernc, @ozars

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2014-10-02.21:32:00.695>
labels = ['3.7', 'type-bug', 'library', '3.9']
title = '-W option cannot use non-standard categories'
updated_at = <Date 2022-03-11.23:18:27.139>
user = 'https://github.com/remram44'

bugs.python.org fields:

activity = <Date 2022-03-11.23:18:27.139>
actor = 'mmerickel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-10-02.21:32:00.695>
creator = 'remram'
dependencies = []
files = []
hgrepos = []
issue_num = 22543
keywords = []
message_count = 8.0
messages = ['228261', '228286', '228287', '228326', '276416', '330700', '359316', '414945']
nosy_count = 10.0
nosy_names = ['pitrou', 'THRlWiTi', 'torsten', 'Gerrit.Holl', 'mitya57', 'mmerickel', 'remram', 'kernc', 'ozars', 'Feng Yu']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22543'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.9']

主要语言
Python
星标
77.2k
派生
36k
平均合并
1 天 9 小时
30 天内合并 PR
558

贡献指南

打开贡献指南

从这里开始

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

python/cpython 的其他 Issue

查看 python/cpython 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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