Doctest should handle situations when test files are not readable

Offen
#59,383 17 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

    Vorherrschende Sprache
    Python
    Sterne
    77.2k
    Forks
    36k
    Ø Merge
    1 T. 9 Std.
    Gemergte PRs (30 T.)
    558

    Beitragsleitfaden

    Beitragsleitfaden öffnen

    Erste Schritte

    1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
    2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
    3. Forken Sie das Repository und arbeiten Sie in einem Branch.
    4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

    Mehr aus python/cpython

    Alle Issues in python/cpython

    Ähnliche Issues

    Weitere Issues zu Python

    Neue Issues direkt in Ihr Postfach

    Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.