File truncate() not defaulting to current position as documented

Open
#70,346 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the documentation and I/O behavior for file truncate(), focusing on the documented default position and the reported mismatch. The issue provides no file or test names; done means resolving whether the implementation or documentation is incorrect and making the behavior and documentation agree.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) docs topic-IO type-bug
BPO 26158
Nosy @pitrou, @benjaminp, @socketpair, @vadmium, @serhiy-storchaka, @eryksun, @zooba

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 2016-01-19.15:19:44.966>
labels = ['type-bug', '3.8', '3.9', 'expert-IO', '3.10', 'docs']
title = 'File truncate() not defaulting to current position as documented'
updated_at = <Date 2021-02-26.17:25:06.794>
user = 'https://bugs.python.org/fornax'

bugs.python.org fields:

activity = <Date 2021-02-26.17:25:06.794>
actor = 'eryksun'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'IO']
creation = <Date 2016-01-19.15:19:44.966>
creator = 'fornax'
dependencies = []
files = []
hgrepos = []
issue_num = 26158
keywords = []
message_count = 15.0
messages = ['258600', '258611', '258612', '258613', '258614', '258615', '258617', '258618', '258619', '258622', '258624', '258626', '258634', '258637', '258639']
nosy_count = 12.0
nosy_names = ['pitrou', 'benjamin.peterson', 'stutzbach', 'Zero', 'docs@python', 'socketpair', 'martin.panter', 'serhiy.storchaka', 'eryksun', 'steve.dower', 'random832', 'fornax']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26158'
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

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.