concurrent.futures.threading: Add a timeout to Executor shutdown() method
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27978 |
|---|---|
| Nosy | @pitrou |
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 2016-09-06.18:49:39.355>
labels = ['3.8', 'type-feature', 'library']
title = 'concurrent.futures.threading: Add a timeout to Executor shutdown() method'
updated_at = <Date 2021-09-26.21:19:09.922>
user = 'https://bugs.python.org/PatrikDufresne'
bugs.python.org fields:
activity = <Date 2021-09-26.21:19:09.922>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-09-06.18:49:39.355>
creator = 'Patrik Dufresne'
dependencies = []
files = []
hgrepos = []
issue_num = 27978
keywords = []
message_count = 1.0
messages = ['274599']
nosy_count = 2.0
nosy_names = ['pitrou', 'Patrik Dufresne']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27978'
versions = ['Python 3.8']
Linked PRs
- gh-157215
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 Executor shutdown() entry point and review linked PR gh-157215 to understand the proposed timeout API and current state of the work. Compare that proposal with the issue request, then verify that the resulting behavior covers timeout handling and that the work is complete without conflicting with the existing pull request.
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
- Needs clarification
- Newbie friendliness
- 25/100