Return results from doctest.run_docstring_examples()

Open
#65,325 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the doctest.run_docstring_examples() entry point and inspect the linked doctest.patch for the proposed behavior. Trace the surrounding doctest implementation and determine how the function should expose its results; done means the requested results are returned consistently.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 21126
Nosy @tim-one, @giampaolo, @rbtcollins, @zware
Files
  • doctest.patch
    		•

    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-01.18:12:24.662>
labels = ['type-feature']
title = 'Return results from doctest.run_docstring_examples()'
updated_at = <Date 2015-08-12.21:36:09.401>
user = 'https://github.com/giampaolo'

    bugs.python.org fields:

    activity = <Date 2015-08-12.21:36:09.401>
actor = 'rbcollins'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2014-04-01.18:12:24.662>
creator = 'giampaolo.rodola'
dependencies = []
files = ['34697']
hgrepos = []
issue_num = 21126
keywords = ['patch']
message_count = 3.0
messages = ['215335', '247729', '248476']
nosy_count = 4.0
nosy_names = ['tim.peters', 'giampaolo.rodola', 'rbcollins', 'zach.ware']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21126'
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.