Doctest capture only AssertionError but not printed text
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- python
- Área
- testing-qa
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 21183 |
|---|---|
| Nosy | @tim-one, @stevendaprano, @osantana |
| Files |
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']
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python/cpython
-
docs pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
build type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
stdlib topic-email type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de python/cpython
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
PolicyEngine/policyengine-us#9559 ·
-
priority: p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
googleapis/librarian#7636 ·
-
from:qa priority:P2 reliability tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
spec-kitty/spec-kitty#4874 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100