Add an explanation what happens with subprocess parent and child processes when signals are sent
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation, operating-systems
Research direction
Start by running bug.py and interrupting it partway, as the issue describes, to observe the subprocess parent and child behavior. Then find the relevant Python documentation section and add an explanation of what happens when signals are sent; done means the documented behavior matches the observed scenario.
Written by the indexing model from the issue text.
Description
| BPO | 25787 |
|---|---|
| Nosy | @vadmium |
| Files |
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 2015-12-03.03:29:39.823>
labels = ['docs']
title = 'Add an explanation what happens with subprocess parent and child processes when signals are sent'
updated_at = <Date 2015-12-09.10:32:22.544>
user = 'https://bugs.python.org/krichter'
bugs.python.org fields:
activity = <Date 2015-12-09.10:32:22.544>
actor = 'martin.panter'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-12-03.03:29:39.823>
creator = 'krichter'
dependencies = []
files = ['41273']
hgrepos = []
issue_num = 25787
keywords = []
message_count = 5.0
messages = ['255802', '255831', '255845', '256147', '256153']
nosy_count = 4.0
nosy_names = ['docs@python', 'martin.panter', 'krichter', 'Ian Macartney']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue25787'
versions = ['Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·