multiprocessing.Connection does not communicate pipe closure between parent and child

未關閉
#56,697 10 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python
領域
documentation

研究方向

No source file or test is named. Start by reading the multiprocessing.Connection documentation and the linked BPO issue, then reproduce the parent/child pipe-closure behavior to determine whether the documented behavior or implementation is incorrect. Done means the closure behavior is clearly resolved and covered by the appropriate documentation or test.

由索引模型根據 Issue 內容生成。

描述

3.10 3.8 (EOL) 3.9 (EOL) docs topic-multiprocessing type-bug
BPO 12488
Nosy @pitrou

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-07-04.11:43:29.105>
labels = ['type-bug', '3.8', '3.9', '3.10', 'docs']
title = 'multiprocessing.Connection does not communicate pipe closure between parent and child'
updated_at = <Date 2020-11-14.11:11:23.404>
user = 'https://bugs.python.org/lcampagn'

bugs.python.org fields:

activity = <Date 2020-11-14.11:11:23.404>
actor = 'neologix'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2011-07-04.11:43:29.105>
creator = 'lcampagn'
dependencies = []
files = []
hgrepos = []
issue_num = 12488
keywords = []
message_count = 8.0
messages = ['139754', '139765', '139769', '139788', '139789', '139791', '139792', '159282']
nosy_count = 4.0
nosy_names = ['syeberman', 'pitrou', 'docs@python', 'lcampagn']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12488'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

主要語言
Python
星號
77.2k
分支
36k
平均合併
1 天 9 小時
30 天內合併 PR
558

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

python/cpython 的其他 Issue

查看 python/cpython 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。