unsynchronized write pointer in io.TextIOWrapper in 'r+' mode
Open
Nobody has claimed this yet.
stdlib
topic-IO
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38710 |
|---|---|
| Nosy | @vadmium, @MojoVampire |
| Superseder |
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-11-06.04:04:15.160>
labels = ['3.7', 'type-bug', 'library', 'expert-IO']
title = "unsynchronized write pointer in io.TextIOWrapper in 'r+' mode"
updated_at = <Date 2019-11-17.23:20:53.209>
user = 'https://bugs.python.org/ManuelIgnacioPrezAlcolea'
bugs.python.org fields:
activity = <Date 2019-11-17.23:20:53.209>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'IO']
creation = <Date 2019-11-06.04:04:15.160>
creator = 'Manuel Ignacio P\xc3\xa9rez Alcolea'
dependencies = []
files = []
hgrepos = []
issue_num = 38710
keywords = []
message_count = 2.0
messages = ['356089', '356835']
nosy_count = 3.0
nosy_names = ['martin.panter', 'josh.r', 'Manuel Ignacio P\xc3\xa9rez Alcolea']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = '12215'
type = 'behavior'
url = 'https://bugs.python.org/issue38710'
versions = ['Python 3.7']
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
Start with io.TextIOWrapper and the migrated BPO record for issue 38710. Check superseding issue 12215 before doing work; this issue names no files, tests, reproduction steps, or linked pull request, so its completion criteria are not specified here.
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
- 20/100