warnings module offers no documented, programmatic way to reset "seen-warning" flag

未關閉
#64,330 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
20/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
python
領域
backend

研究方向

The payload names no files or tests. Start with the warnings module and the superseding bpo-20131 issue, then identify the relevant API and documentation entry points; done means an agreed programmatic way to reset the seen-warning state is documented.

由索引模型根據 Issue 內容生成。

描述

stdlib type-feature
BPO 20131
Nosy @bitdancer, @catherinedevlin
Superseder
  • bpo-20131: warnings module offers no documented, programmatic way to reset "seen-warning" flag
    		•

    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-01-05.12:39:29.374>
labels = ['type-feature', 'library']
title = 'warnings module offers no documented, programmatic way to reset "seen-warning" flag'
updated_at = <Date 2021-05-18.14:00:44.784>
user = 'https://bugs.python.org/inducer'

    bugs.python.org fields:

    activity = <Date 2021-05-18.14:00:44.784>
actor = 'Catherine.Devlin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-01-05.12:39:29.374>
creator = 'inducer'
dependencies = []
files = []
hgrepos = []
issue_num = 20131
keywords = []
message_count = 3.0
messages = ['207372', '207390', '393873']
nosy_count = 3.0
nosy_names = ['inducer', 'r.david.murray', 'Catherine.Devlin']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'test needed'
status = 'open'
superseder = '20131'
type = 'enhancement'
url = 'https://bugs.python.org/issue20131'
versions = ['Python 3.5']

    主要語言
    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 摘要。