Improve reporting of broken stdout pipe during interpreter shutdown
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 25/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- python
研究方向
Start by reviewing python-sigint_and_epipe_straces.txt and flush_stdout_at_shutdown.patch, the historical evidence and proposed change attached to this issue. Determine the current interpreter-shutdown behavior for a broken stdout pipe and define improved reporting before validating the result with an appropriate regression test.
由索引模型根據 Issue 內容生成。
描述
| BPO | 11380 |
|---|---|
| Nosy | @terryjreedy, @ncoghlan, @pitrou, @rbtcollins, @florentx, @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 2011-03-03.01:32:45.546>
labels = ['type-bug', 'expert-IO']
title = 'Improve reporting of broken stdout pipe during interpreter shutdown'
updated_at = <Date 2018-06-16.10:13:08.003>
user = 'https://bugs.python.org/ulidtko'
bugs.python.org fields:
activity = <Date 2018-06-16.10:13:08.003>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2011-03-03.01:32:45.546>
creator = 'ulidtko'
dependencies = []
files = ['24517', '31853']
hgrepos = []
issue_num = 11380
keywords = ['patch']
message_count = 16.0
messages = ['129930', '130083', '153320', '198316', '198332', '198338', '198339', '198345', '198347', '198349', '213109', '248574', '248579', '248625', '248626', '319729']
nosy_count = 11.0
nosy_names = ['terry.reedy', 'ncoghlan', 'pitrou', 'rbcollins', 'zzzeek', 'flox', 'ulidtko', 'martin.panter', 'Jeremy.Fishman', 'daumiller', 'Christopher.Heiny']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11380'
versions = ['Python 2.7']
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- 平均合併
- 1 天 9 小時
- 30 天內合併 PR
- 558
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
python/cpython 的其他 Issue
-
docs pending
難度 2/5 1-3 小時 新手友好度 78/100
-
stdlib type-feature
難度 2/5 1-3 小時 新手友好度 78/100
-
stdlib type-feature
難度 2/5 1-3 小時 新手友好度 72/100
-
build type-bug
難度 2/5 1-3 小時 新手友好度 76/100
-
stdlib topic-email type-feature
難度 2/5 1-3 小時 新手友好度 70/100
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 90/100
-
bug
難度 2/5 1-3 小時 新手友好度 86/100
zostera/django-bootstrap4#894 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
use-agent-os/agent-os#3276 ·
-
難度 2/5 1-3 小時 新手友好度 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
難度 2/5 1-3 小時 新手友好度 88/100
NousResearch/hermes-agent#117848 ·