Add a "message" action to warnings, to trigger for every *unique* message
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41641 |
|---|---|
| Nosy | @masklinn |
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 2020-08-26.09:11:26.612>
labels = ['type-feature', 'library', '3.9']
title = 'Add a "message" action to warnings, to trigger for every *unique* message'
updated_at = <Date 2020-08-26.09:11:26.612>
user = 'https://github.com/masklinn'
bugs.python.org fields:
activity = <Date 2020-08-26.09:11:26.612>
actor = 'xmorel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-08-26.09:11:26.612>
creator = 'xmorel'
dependencies = []
files = []
hgrepos = []
issue_num = 41641
keywords = []
message_count = 1.0
messages = ['375924']
nosy_count = 1.0
nosy_names = ['xmorel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41641'
versions = ['Python 3.9']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names only the Library (Lib) component and no files or tests; begin by locating the warnings implementation and its existing action handling. Add coverage for triggering the action once per unique message, and use those tests to verify the requested behavior is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100