Add a timeout to multiprocessing's Pool.join
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31782 |
|---|---|
| Nosy | @pitrou, @applio |
| Files |
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 2017-10-13.19:23:42.800>
labels = ['3.7', 'type-feature', 'library']
title = "Add a timeout to multiprocessing's Pool.join"
updated_at = <Date 2017-10-20.17:05:24.169>
user = 'https://bugs.python.org/WillStarms'
bugs.python.org fields:
activity = <Date 2017-10-20.17:05:24.169>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-10-13.19:23:42.800>
creator = 'Will Starms'
dependencies = []
files = ['47219', '47220']
hgrepos = []
issue_num = 31782
keywords = ['patch']
message_count = 3.0
messages = ['304350', '304352', '304515']
nosy_count = 3.0
nosy_names = ['pitrou', 'davin', 'Will Starms']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31782'
versions = ['Python 3.7']
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 multiprocessing.Pool.join and compare the attached cpython_timeout.patch and cpython_raise_timeout.patch. Determine which timeout and expiry behavior is intended; the work is complete when Pool.join supports that behavior consistently and the relevant multiprocessing tests cover it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100