recursive ProcessPoolExecutor invoke unable to return result
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45761 |
|---|---|
| Nosy | @brianquinlan, @pitrou |
| 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 2021-11-09.08:15:50.060>
labels = ['type-bug', 'library', '3.9']
title = 'recursive ProcessPoolExecutor invoke unable to return result'
updated_at = <Date 2021-11-12.21:50:38.365>
user = 'https://bugs.python.org/evan0greenup'
bugs.python.org fields:
activity = <Date 2021-11-12.21:50:38.365>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-11-09.08:15:50.060>
creator = 'evan0greenup'
dependencies = []
files = ['50431', '50432']
hgrepos = []
issue_num = 45761
keywords = []
message_count = 1.0
messages = ['406003']
nosy_count = 3.0
nosy_names = ['bquinlan', 'pitrou', 'evan0greenup']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45761'
versions = ['Python 3.9']
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 by reviewing the two attached hello.py files and the ProcessPoolExecutor entry points they exercise. Reproduce the recursive invocation behavior and trace why the result is not returned; done means the reported recursive case returns its expected result without regressing executor behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100