Display exit-codes for abruptly terminated processes in concurrent.futures
Open
Nobody has claimed this yet.
3.10
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 41125 |
|---|---|
| Nosy | @EpicWink |
| PRs |
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-26.05:18:59.747>
labels = ['type-feature', 'library', '3.10']
title = 'Display exit-codes for abruptly terminated processes in concurrent.futures'
updated_at = <Date 2020-06-26.07:25:13.866>
user = 'https://github.com/EpicWink'
bugs.python.org fields:
activity = <Date 2020-06-26.07:25:13.866>
actor = 'Epic_Wink'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-06-26.05:18:59.747>
creator = 'Epic_Wink'
dependencies = []
files = []
hgrepos = []
issue_num = 41125
keywords = ['patch']
message_count = 1.0
messages = ['372409']
nosy_count = 1.0
nosy_names = ['Epic_Wink']
pr_nums = ['21166']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41125'
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
Review PR #21166 and the concurrent.futures implementation first; the issue names no files or tests. Confirm how abruptly terminated processes are currently reported and define completion as displaying their exit codes through the relevant concurrent.futures behavior, with coverage for the resulting output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100