Doctest sees directives in strings when it should only see them in comments

Ouverte
#56,118 8 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python
Domaine
testing

Piste de recherche

Start by reviewing comments.diff, comments2.diff, and comments3.diff, the implementation artifacts named in the issue, then locate doctest’s directive parsing entry point. The change is done when directives inside strings are ignored while directives in comments are still recognized; run the relevant doctest tests to verify both cases.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

stdlib type-feature
BPO 11909
Nosy @tim-one, @benjaminp, @ssbr, @bitdancer, @akheron
Files
  • comments.diff: patch to tip
  • comments2.diff
  • comments3.diff
    		•

    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 2011-04-22.19:31:22.132>
labels = ['type-feature', 'library']
title = 'Doctest sees directives in strings when it should only see them in comments'
updated_at = <Date 2011-07-04.03:45:34.894>
user = 'https://github.com/ssbr'

    bugs.python.org fields:

    activity = <Date 2011-07-04.03:45:34.894>
actor = 'Devin Jeanpierre'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-04-22.19:31:22.132>
creator = 'Devin Jeanpierre'
dependencies = []
files = ['21757', '22559', '22562']
hgrepos = []
issue_num = 11909
keywords = ['patch']
message_count = 8.0
messages = ['134278', '138780', '138886', '138893', '138948', '139715', '139721', '139732']
nosy_count = 5.0
nosy_names = ['tim.peters', 'benjamin.peterson', 'Devin Jeanpierre', 'r.david.murray', 'petri.lehtinen']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11909'
versions = ['Python 3.3']

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.