Thread primitives do not report the OS-level error on failure
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32511 |
|---|---|
| Nosy | @nitishch, @drydenb |
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 2018-01-07.15:50:08.335>
labels = ['3.7', '3.8', 'type-bug', 'library']
title = 'Thread primitives do not report the OS-level error on failure'
updated_at = <Date 2018-01-08.03:48:55.110>
user = 'https://bugs.python.org/zwol'
bugs.python.org fields:
activity = <Date 2018-01-08.03:48:55.110>
actor = 'nitishch'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-01-07.15:50:08.335>
creator = 'zwol'
dependencies = []
files = []
hgrepos = []
issue_num = 32511
keywords = []
message_count = 1.0
messages = ['309623']
nosy_count = 3.0
nosy_names = ['zwol', 'nitishch', 'drydenb']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32511'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8']
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
Start with the linked BPO issue 32511 and review the CPython library code implementing thread primitives. Trace their failure paths and determine where OS-level errors are lost; done means failures expose the underlying OS error and the behavior is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100