ValueError: can't have unbuffered text I/O for io.open(1, 'wt', 0)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the reported call, io.open(1, 'wt', 0), and inspect Python's IO component to determine whether the ValueError is expected or indicates a bug. The issue does not name source files or tests; done should include an agreed behavior and coverage for the unbuffered text-I/O case.
Written by the indexing model from the issue text.
Description
| BPO | 17404 |
|---|---|
| Nosy | @amauryfa, @pitrou, @rbtcollins, @benjaminp, @hynek, @vadmium, @serhiy-storchaka |
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-03-12.14:42:40.965>
labels = ['3.10', 'type-bug', '3.8', '3.9', 'expert-IO']
title = "ValueError: can't have unbuffered text I/O for io.open(1,\t'wt', 0)"
updated_at = <Date 2020-11-06.22:51:34.480>
user = 'https://github.com/rbtcollins'
bugs.python.org fields:
activity = <Date 2020-11-06.22:51:34.480>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2013-03-12.14:42:40.965>
creator = 'rbcollins'
dependencies = []
files = []
hgrepos = []
issue_num = 17404
keywords = []
message_count = 7.0
messages = ['184025', '184040', '184041', '184045', '184072', '184073', '332739']
nosy_count = 8.0
nosy_names = ['amaury.forgeotdarc', 'pitrou', 'rbcollins', 'benjamin.peterson', 'stutzbach', 'hynek', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17404'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·