python / python/cpython

Multiprocessing docs don't describe thread-safety

Open
#84,992 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs topic-multiprocessing
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 40815
Nosy @alanbriolat, @bensimner, @iritkatriel

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-05-29.13:25:00.812>
labels = ['docs']
title = "Multiprocessing docs don't describe thread-safety"
updated_at = <Date 2020-08-17.18:29:13.905>
user = 'https://github.com/bensimner'

bugs.python.org fields:

activity = <Date 2020-08-17.18:29:13.905>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-05-29.13:25:00.812>
creator = 'bjs'
dependencies = []
files = []
hgrepos = []
issue_num = 40815
keywords = []
message_count = 3.0
messages = ['370310', '375103', '375563']
nosy_count = 4.0
nosy_names = ['docs@python', 'alan.briolat', 'bjs', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue40815'
versions = []

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.

Research direction

Start with the multiprocessing documentation and the linked BPO issue 40815 to understand the missing thread-safety guidance. Update the relevant documentation so its thread-safety behavior is described clearly, then verify that the resulting text addresses the issue without changing unrelated multiprocessing documentation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.