Clarify requirements for file-like objects
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python
调研方向
Start by reviewing the issue discussion and the referenced iobase.diff attachment; the payload does not identify a documentation file or a precise requirement to clarify. Done would require an agreed scope for the file-like object requirements and corresponding documentation changes, but that completion criterion is not established here.
由索引模型根据 Issue 内容生成。
描述
| BPO | 21763 |
|---|---|
| Nosy | @birkenfeld, @rhettinger, @ncoghlan, @pitrou, @benjaminp, @ezio-melotti, @merwok, @bitdancer, @hynek |
| 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 2014-06-14.22:16:50.648>
labels = ['type-feature', 'docs']
title = 'Clarify requirements for file-like objects'
updated_at = <Date 2014-06-17.21:52:47.726>
user = 'https://bugs.python.org/nikratio'
bugs.python.org fields:
activity = <Date 2014-06-17.21:52:47.726>
actor = 'ncoghlan'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2014-06-14.22:16:50.648>
creator = 'nikratio'
dependencies = []
files = ['35636']
hgrepos = []
issue_num = 21763
keywords = ['patch']
message_count = 15.0
messages = ['220588', '220647', '220663', '220680', '220685', '220687', '220777', '220830', '220875', '220878', '220879', '220880', '220883', '220888', '220901']
nosy_count = 12.0
nosy_names = ['georg.brandl', 'rhettinger', 'ncoghlan', 'pitrou', 'benjamin.peterson', 'stutzbach', 'ezio.melotti', 'eric.araujo', 'r.david.murray', 'nikratio', 'docs@python', 'hynek']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21763'
versions = ['Python 3.4', 'Python 3.5']
- 主要语言
- 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
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 86/100
-
🐛 Bug 🔔 Pending processing
难度 2/5 1-3 小时 新手友好度 84/100
jumpserver/jumpserver#17584 ·