Incorrect number of running calls in ProcessPoolExecutor
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37276 |
|---|---|
| Nosy | @brianquinlan, @pitrou, @asvetlov, @methane, @ambv, @serhiy-storchaka, @willingc, @pablogsal, @maggyero |
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 2019-06-14.06:08:05.891>
labels = ['3.7', 'type-bug', 'library']
title = 'Incorrect number of running calls in ProcessPoolExecutor'
updated_at = <Date 2019-06-26.12:26:02.838>
user = 'https://github.com/maggyero'
bugs.python.org fields:
activity = <Date 2019-06-26.12:26:02.838>
actor = 'asvetlov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-14.06:08:05.891>
creator = 'maggyero'
dependencies = []
files = []
hgrepos = []
issue_num = 37276
keywords = []
message_count = 11.0
messages = ['345553', '346529', '346538', '346544', '346548', '346565', '346591', '346594', '346596', '346610', '346611']
nosy_count = 9.0
nosy_names = ['bquinlan', 'pitrou', 'asvetlov', 'methane', 'lukasz.langa', 'serhiy.storchaka', 'willingc', 'pablogsal', 'maggyero']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37276'
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 by reviewing BPO issue 37276 and the Python 3.7 Library (Lib) component; the payload names no source file, test, reproduction, or acceptance criterion. Locate the affected ProcessPoolExecutor entry point, establish how the running-call count becomes incorrect, and define a focused regression test whose corrected count marks the work as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100