open() of read-write non-seekable streams broken

未关闭
#64,273 20 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
python
领域
backend

调研方向

Start by reproducing the read-write non-seekable stream behavior described in the title and inspect the Python IO component. No source file or test is named, so locate the relevant open() implementation and existing IO tests first. Done means the broken behavior is corrected and covered by a regression test.

由索引模型根据 Issue 内容生成。

描述

topic-IO type-bug
BPO 20074
Nosy @pitrou, @benjaminp, @bitdancer, @hynek, @vadmium, @serhiy-storchaka, @cagney

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 2013-12-26.20:01:49.042>
labels = ['type-bug', 'expert-IO']
title = 'open() of read-write non-seekable streams broken'
updated_at = <Date 2021-03-02.13:41:06.954>
user = 'https://bugs.python.org/Dolda2000'

bugs.python.org fields:

activity = <Date 2021-03-02.13:41:06.954>
actor = 'ken.teh'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2013-12-26.20:01:49.042>
creator = 'Dolda2000'
dependencies = []
files = []
hgrepos = []
issue_num = 20074
keywords = []
message_count = 19.0
messages = ['206957', '206960', '206961', '206980', '206981', '206982', '206983', '206991', '206998', '207001', '207002', '207003', '207010', '207012', '273258', '339809', '366115', '366117', '387929']
nosy_count = 12.0
nosy_names = ['pitrou', 'benjamin.peterson', 'stutzbach', 'r.david.murray', 'python-dev', 'hynek', 'martin.panter', 'pavlix', 'serhiy.storchaka', 'Dolda2000', 'cagney', 'ken.teh']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20074'
versions = ['Python 3.3', 'Python 3.4']

主要语言
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 摘要。