multiprocessing.dummy.Pool does not accept maxtasksperchild argument

Open
#61,329 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start at the multiprocessing.dummy.Pool entry point and inspect how its arguments are defined, focusing on the missing maxtasksperchild option. Locate the related standard-library tests and use them to verify that Pool accepts the argument with the expected behavior.

Written by the indexing model from the issue text.

Description

stdlib topic-multiprocessing type-bug
BPO 17127
Nosy @MojoVampire

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 2013-02-04.18:28:33.495>
labels = ['type-bug', 'library']
title = 'multiprocessing.dummy.Pool does not accept maxtasksperchild argument'
updated_at = <Date 2019-04-26.20:01:33.816>
user = 'https://bugs.python.org/NoahYetter'

bugs.python.org fields:

activity = <Date 2019-04-26.20:01:33.816>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-04.18:28:33.495>
creator = 'Noah.Yetter'
dependencies = []
files = []
hgrepos = []
issue_num = 17127
keywords = []
message_count = 4.0
messages = ['181365', '223364', '223394', '223395']
nosy_count = 4.0
nosy_names = ['jnoller', 'sbt', 'Noah.Yetter', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17127'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.