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

Open
#64,330 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

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.

Written by the indexing model from the issue text.

Description

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']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.