Should io.TextIOWrapper raise an error at instantiation if a StringIO is passed as 'buffer'?
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
stdlib
topic-IO
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 38029 |
|---|---|
| Nosy | @bskinn |
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 2019-09-04.16:09:55.125>
labels = ['3.8', 'type-bug', 'library', '3.9']
title = "Should io.TextIOWrapper raise an error at instantiation if a StringIO is passed as 'buffer'?"
updated_at = <Date 2019-09-04.16:09:55.125>
user = 'https://github.com/bskinn'
bugs.python.org fields:
activity = <Date 2019-09-04.16:09:55.125>
actor = 'bskinn'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-09-04.16:09:55.125>
creator = 'bskinn'
dependencies = []
files = []
hgrepos = []
issue_num = 38029
keywords = []
message_count = 1.0
messages = ['351139']
nosy_count = 1.0
nosy_names = ['bskinn']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38029'
versions = ['Python 3.8', 'Python 3.9']
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.
Research direction
The issue names io.TextIOWrapper and StringIO but does not identify a source file or test. Start by reproducing the instantiation behavior and reading the relevant io implementation and existing tests. Done means reaching an agreed behavior for this buffer combination and covering it with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100