Report actual EOF character instead of assuming Ctrl-D

Open
#66,506 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Review the attached lib_site_py.gdiff first, then locate the corresponding current CPython library entry point. No test file is named, so identify the relevant library test before making the change; done means the reported EOF character comes from the actual value rather than an assumed Ctrl-D.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 22310
Nosy @vstinner
Files
  • lib_site_py.gdiff: Lookup actual EOF character instead of assuming Ctrl-D
    		•

    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 2014-08-30.23:31:56.575>
labels = ['type-feature', 'library']
title = 'Report actual EOF character instead of assuming Ctrl-D'
updated_at = <Date 2014-08-31.14:14:33.984>
user = 'https://bugs.python.org/JohnMalmberg'

    bugs.python.org fields:

    activity = <Date 2014-08-31.14:14:33.984>
actor = 'John.Malmberg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-08-30.23:31:56.575>
creator = 'John.Malmberg'
dependencies = []
files = ['36511']
hgrepos = []
issue_num = 22310
keywords = []
message_count = 4.0
messages = ['226154', '226172', '226173', '226180']
nosy_count = 2.0
nosy_names = ['vstinner', 'John.Malmberg']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22310'
versions = ['Python 3.5']

    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.