Cannot use ProcessPoolExecutor if in a decorator?
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41577 |
|---|---|
| Nosy | @pitrou, @avassalotti, @aeros |
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-08-18.17:21:46.050>
labels = ['3.7', '3.8', 'type-bug', 'library', '3.9']
title = 'Cannot use ProcessPoolExecutor if in a decorator?'
updated_at = <Date 2020-08-19.03:12:40.247>
user = 'https://bugs.python.org/bobfanglondon'
bugs.python.org fields:
activity = <Date 2020-08-19.03:12:40.247>
actor = 'aeros'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-08-18.17:21:46.050>
creator = 'bob.fang.london'
dependencies = []
files = []
hgrepos = []
issue_num = 41577
keywords = []
message_count = 2.0
messages = ['375614', '375632']
nosy_count = 4.0
nosy_names = ['pitrou', 'alexandre.vassalotti', 'aeros', 'bob.fang.london']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41577'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', '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 reading the migrated BPO 41577 discussion and the ProcessPoolExecutor documentation, then reproduce the reported decorator use case. Identify the relevant standard-library implementation and existing tests before determining what behavior should change; done requires a confirmed fix or a clear explanation backed by a regression test.
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