Occasionally check for Ctrl-C in long-running operations like sum
未關閉
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 冷清
- 技術堆疊
- python
研究方向
Start by reviewing KeyboardInterrupt.patch and test_sig_int_builtins.py, the files attached to this issue. Check how the proposed tests exercise Ctrl-C during long-running built-in operations such as sum. Done means the relevant built-ins can be interrupted and the regression tests pass.
由索引模型根據 Issue 內容生成。
描述
3.7 (EOL)
interpreter-core
type-bug
| BPO | 26351 |
|---|---|
| Nosy | @rhettinger, @terryjreedy, @ncoghlan, @vstinner, @stevendaprano, @wimglenn, @treyhunner |
| 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 2016-02-12.17:47:32.154>
labels = ['interpreter-core', 'type-bug', '3.7']
title = 'Occasionally check for Ctrl-C in long-running operations like sum'
updated_at = <Date 2016-09-30.14:54:40.369>
user = 'https://github.com/stevendaprano'
bugs.python.org fields:
activity = <Date 2016-09-30.14:54:40.369>
actor = 'trey'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-02-12.17:47:32.154>
creator = 'steven.daprano'
dependencies = []
files = ['44746', '44747']
hgrepos = []
issue_num = 26351
keywords = ['patch']
message_count = 15.0
messages = ['260189', '260238', '260535', '260536', '260556', '276995', '276996', '277002', '277094', '277096', '277098', '277185', '277190', '277220', '277757']
nosy_count = 8.0
nosy_names = ['rhettinger', 'terry.reedy', 'ncoghlan', 'vstinner', 'steven.daprano', 'wim.glenn', 'gslavin', 'trey']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26351'
versions = ['Python 3.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