InteractiveInterpreter always prints to stdout

Open
#68,783 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the InteractiveInterpreter entry point and the attached issue24595.diff, then reproduce how its output is currently routed. Review the existing library tests around this behavior, if present, and define done as output no longer being unconditionally written to stdout while preserving normal interactive behavior.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 24595
Nosy @terryjreedy, @bitdancer, @berkerpeksag, @vadmium
Files
  • issue24595.diff
    		•

    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 2015-07-09.13:00:12.002>
labels = ['type-feature', 'library']
title = 'InteractiveInterpreter always prints to stdout'
updated_at = <Date 2015-12-10.20:11:07.329>
user = 'https://bugs.python.org/graphite'

    bugs.python.org fields:

    activity = <Date 2015-12-10.20:11:07.329>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-07-09.13:00:12.002>
creator = 'graphite'
dependencies = []
files = ['41279']
hgrepos = []
issue_num = 24595
keywords = ['patch']
message_count = 7.0
messages = ['246487', '246511', '246598', '247976', '247984', '256179', '256181']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'r.david.murray', 'berker.peksag', 'martin.panter', 'graphite']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24595'
versions = ['Python 3.6']

    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.