Doctest capture only AssertionError but not printed text

Open
#65,382 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

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.

Written by the indexing model from the issue text.

Description

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

    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.