TextIOWrapper.seek silently wraps around on very large offsets

Open
#91,112 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the TextIOWrapper.seek behavior described in this issue and review the linked BPO issue 46956. Reproduce the silent wraparound using a very large offset, then identify the relevant CPython IO implementation and tests. Done means the behavior is addressed with regression coverage, but the issue does not name a file or test to use.

Written by the indexing model from the issue text.

Description

3.7 (EOL) topic-IO type-bug
BPO 46956
Nosy @csernazs, @vlaci

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 2022-03-08.10:09:03.427>
labels = ['type-bug', '3.7', 'expert-IO']
title = 'TextIOWrapper.seek silently wraps around on very large offsets'
updated_at = <Date 2022-03-08.10:52:26.126>
user = 'https://github.com/vlaci'

bugs.python.org fields:

activity = <Date 2022-03-08.10:52:26.126>
actor = 'csernazs'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2022-03-08.10:09:03.427>
creator = 'vlaci'
dependencies = []
files = []
hgrepos = []
issue_num = 46956
keywords = []
message_count = 1.0
messages = ['414745']
nosy_count = 2.0
nosy_names = ['csernazs', 'vlaci']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46956'
versions = ['Python 3.7']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.