Log exception never retrieved in concurrent.futures
Open
Nobody has claimed this yet.
3.10
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41372 |
|---|---|
| Nosy | @brianquinlan, @pitrou, @bharel |
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-07-22.22:39:11.131>
labels = ['type-feature', 'library', '3.10']
title = 'Log exception never retrieved in concurrent.futures'
updated_at = <Date 2020-07-22.22:42:11.330>
user = 'https://github.com/bharel'
bugs.python.org fields:
activity = <Date 2020-07-22.22:42:11.330>
actor = 'bar.harel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-07-22.22:39:11.131>
creator = 'bar.harel'
dependencies = []
files = []
hgrepos = []
issue_num = 41372
keywords = []
message_count = 1.0
messages = ['374114']
nosy_count = 3.0
nosy_names = ['bquinlan', 'pitrou', 'bar.harel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41372'
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
Start at Python's concurrent.futures library and read the issue title alongside its original tracker entry for the intended exception-logging behavior. Define what should happen when a future's exception is never retrieved, then identify the relevant tests and update them to demonstrate that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100