multiprocessing.reduction is undocumented

Open
#63,037 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by locating the multiprocessing.reduction module and the existing multiprocessing documentation. The issue does not name documentation files, symbols, or tests, so confirm the intended scope and placement with maintainers before making changes; done means the module is covered by the project’s documentation.

Written by the indexing model from the issue text.

Description

3.7 (EOL) docs topic-multiprocessing
BPO 18837
Nosy @RonaldAJ

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-08-26.06:56:10.402>
labels = ['3.7', 'docs']
title = 'multiprocessing.reduction is undocumented'
updated_at = <Date 2020-02-24.10:45:24.213>
user = 'https://bugs.python.org/tpievila'

bugs.python.org fields:

activity = <Date 2020-02-24.10:45:24.213>
actor = 'Rajve'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2013-08-26.06:56:10.402>
creator = 'tpievila'
dependencies = []
files = []
hgrepos = []
issue_num = 18837
keywords = []
message_count = 2.0
messages = ['196184', '362584']
nosy_count = 5.0
nosy_names = ['jnoller', 'docs@python', 'sbt', 'tpievila', 'Rajve']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue18837'
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.