Add keepends option to readline() and readlines()

Open
#84,044 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

The requested entry points are readline() and readlines(); start by locating their existing implementations and behavior in Python's I/O subsystem. Define completion by supporting the keepends option consistently for both methods and adding coverage for its line-ending behavior.

Written by the indexing model from the issue text.

Description

extension-modules stdlib topic-IO type-feature
BPO 39863
Nosy @methane, @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 2020-03-05.12:37:08.420>
labels = ['3.9', 'expert-IO']
title = 'Add trimend option to readline() and readlines()'
updated_at = <Date 2020-03-06.05:35:01.867>
user = 'https://github.com/methane'

bugs.python.org fields:

activity = <Date 2020-03-06.05:35:01.867>
actor = 'methane'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2020-03-05.12:37:08.420>
creator = 'methane'
dependencies = []
files = []
hgrepos = []
issue_num = 39863
keywords = []
message_count = 3.0
messages = ['363430', '363444', '363485']
nosy_count = 2.0
nosy_names = ['methane', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39863'
versions = ['Python 3.9']

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.