Doctest capture only AssertionError but not printed text

未关闭
#65,382 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Start with the reproducing example in doctest_bug.py and run it to observe the difference between the AssertionError and printed text. Then trace the doctest library behavior responsible for capturing failures. Done means the reported output includes the relevant printed text as well as the assertion failure, with regression coverage for the example.

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

描述

stdlib type-feature
BPO 21183
Nosy @tim-one, @stevendaprano, @osantana
Files
  • doctest_bug.py: Example that reproduces error
    		•

    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-04-09.02:13:50.991>
labels = ['type-feature', 'library']
title = 'Doctest capture only AssertionError but not printed text'
updated_at = <Date 2014-04-09.03:18:12.649>
user = 'https://github.com/osantana'

    bugs.python.org fields:

    activity = <Date 2014-04-09.03:18:12.649>
actor = 'steven.daprano'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-04-09.02:13:50.991>
creator = 'osantana'
dependencies = []
files = ['34771']
hgrepos = []
issue_num = 21183
keywords = []
message_count = 5.0
messages = ['215796', '215797', '215798', '215799', '215800']
nosy_count = 3.0
nosy_names = ['tim.peters', 'steven.daprano', 'osantana']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21183'
versions = ['Python 3.5']

    主要语言
    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 摘要。