multiprocessing.Pool: Need a way to find out if work are finished.

Open
#56,503 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue names multiprocessing.Pool and links the historical 12294.patch; start by reading the current Pool API and reviewing that patch. Determine the intended completion-state behavior and what tests or documentation would be needed to show that the work is complete.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib topic-multiprocessing type-feature
BPO 12294
Nosy @cjrh, @applio, @tirkarthi
Files
  • 12294.patch
    		•

    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 2011-06-09.13:59:51.927>
labels = ['3.7', 'type-feature', 'library']
title = 'multiprocessing.Pool: Need a way to find out if work are finished.'
updated_at = <Date 2018-09-22.17:58:14.013>
user = 'https://bugs.python.org/mozbugbox'

    bugs.python.org fields:

    activity = <Date 2018-09-22.17:58:14.013>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-06-09.13:59:51.927>
creator = 'mozbugbox'
dependencies = []
files = ['24845']
hgrepos = []
issue_num = 12294
keywords = ['patch']
message_count = 2.0
messages = ['137970', '155780']
nosy_count = 6.0
nosy_names = ['mozbugbox', 'jnoller', 'cjrh', 'guilherme-pg', 'davin', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue12294'
versions = ['Python 3.7']

    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.