concurrent.futures as_completed raise TimeoutError wrong
未关闭
还没有人认领这个 Issue。
topic-multiprocessing
type-bug
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 36k
- PR 合并指标
- PR 指标待抓取
描述
| BPO | 29733 |
|---|---|
| Nosy | @MojoVampire, @jiang-wanwei |
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 2017-03-06.11:23:33.813>
labels = ['type-bug']
title = 'concurrent.futures as_completed raise TimeoutError wrong'
updated_at = <Date 2017-03-06.15:48:19.297>
user = 'https://github.com/jiang-wanwei'
bugs.python.org fields:
activity = <Date 2017-03-06.15:48:19.297>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2017-03-06.11:23:33.813>
creator = 'jiangwanwei'
dependencies = []
files = []
hgrepos = []
issue_num = 29733
keywords = []
message_count = 2.0
messages = ['289093', '289116']
nosy_count = 2.0
nosy_names = ['josh.r', 'jiangwanwei']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29733'
versions = ['Python 3.6']
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
调研方向
首先阅读 concurrent.futures.as_completed 入口点，并使用 issue 的 Python 3.6 上下文重现报告的 TimeoutError 行为。找到现有的 concurrent.futures 测试，并在添加回归覆盖之前确定预期的异常行为；issue payload 没有指定文件或测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- backend
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100