InteractiveInterpreter always prints to stdout

未关闭
#68,783 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
cli

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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']

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue，再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库，在一个分支上完成修改。
    4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。