Doctest should handle situations when test files are not readable

Open
#59,383 17 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start with doctest's handling of unreadable test files and review the historical doctest-dont-end-with-exception-on-unreadable-files-v6.patch alongside the earlier patch versions. Compare the proposed behavior with the 17-message discussion; done means unreadable files no longer cause doctest to terminate with an exception.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 15178
Nosy @tim-one, @terryjreedy, @bitdancer, @voidspace, @serhiy-storchaka
Files
  • doctest-dont-end-with-exception-on-unreadable-files.patch: Proposed patch to solve the issue
  • doctest-dont-end-with-exception-on-unreadable-files-v2.patch: Catch exception in _test()
  • doctest-dont-end-with-exception-on-unreadable-files-v3.patch
  • doctest-dont-end-with-exception-on-unreadable-files-v4.patch
  • doctest-dont-end-with-exception-on-unreadable-files-v5.patch
  • doctest-dont-end-with-exception-on-unreadable-files-v6.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 2012-06-25.11:01:44.820>
labels = ['type-bug', 'library']
title = 'Doctest should handle situations when test files are not readable'
updated_at = <Date 2019-03-15.22:47:29.268>
user = 'https://bugs.python.org/bkabrda'

    bugs.python.org fields:

    activity = <Date 2019-03-15.22:47:29.268>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-06-25.11:01:44.820>
creator = 'bkabrda'
dependencies = []
files = ['26153', '26155', '26165', '26172', '26239', '37421']
hgrepos = []
issue_num = 15178
keywords = ['patch']
message_count = 17.0
messages = ['163936', '163964', '163965', '163970', '164036', '164043', '164078', '164120', '164441', '164447', '164506', '164508', '164585', '221298', '232500', '232519', '236043']
nosy_count = 6.0
nosy_names = ['tim.peters', 'terry.reedy', 'r.david.murray', 'michael.foord', 'serhiy.storchaka', 'bkabrda']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue15178'
versions = ['Python 2.7', 'Python 3.4', '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.