python / python/cpython

subprocess.Popen: Confusing documentation for restore_signals

Open
#77,166 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

BPO 32985
Nosy @gpshead, @giampaolo, @bitdancer

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 2018-03-02.17:31:25.802>
labels = ['library']
title = 'subprocess.Popen: Confusing documentation for restore_signals'
updated_at = <Date 2018-03-12.00:49:50.776>
user = 'https://bugs.python.org/ntrrgc'

bugs.python.org fields:

activity = <Date 2018-03-12.00:49:50.776>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-03-02.17:31:25.802>
creator = 'ntrrgc'
dependencies = []
files = []
hgrepos = []
issue_num = 32985
keywords = []
message_count = 2.0
messages = ['313146', '313630']
nosy_count = 4.0
nosy_names = ['gregory.p.smith', 'giampaolo.rodola', 'r.david.murray', 'ntrrgc']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue32985'
versions = ['Python 3.6']

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 subprocess.Popen documentation and its restore_signals parameter description. Clarify the wording so the parameter's behavior is unambiguous, then verify that the updated documentation accurately describes the existing behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.