threading.Event.wait_unset()
Open
Nobody has claimed this yet.
3.10
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 40871 |
|---|---|
| Nosy | @BlackLight |
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-06-05.13:42:51.816>
labels = ['type-feature', 'library', '3.10']
title = 'threading.Event.wait_unset()'
updated_at = <Date 2020-09-25.14:00:30.112>
user = 'https://bugs.python.org/JacobKunnappally'
bugs.python.org fields:
activity = <Date 2020-09-25.14:00:30.112>
actor = 'BlackLight'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-06-05.13:42:51.816>
creator = 'Jacob Kunnappally'
dependencies = []
files = []
hgrepos = []
issue_num = 40871
keywords = []
message_count = 2.0
messages = ['370761', '377492']
nosy_count = 2.0
nosy_names = ['Jacob Kunnappally', 'BlackLight']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40871'
versions = ['Python 3.10']
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 no source file, test, or semantics beyond a proposed threading.Event.wait_unset() method. Read the existing threading.Event implementation and tests, then use linked BPO issue 40871 and the surrounding API behavior to establish the contract before assessing the implementation and required test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100