trace module cannot produce coverage reports for zipped modules

Abierto
#54,551 12 comentarios 0 reacciones 1 asignado Ver en GitHub

@abalkin ya está trabajando en esto.

Desde el 6/11/2010.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

3.7 (EOL) stdlib type-bug
BPO 10342
Nosy @terryjreedy, @abalkin, @vstinner, @PCManticore
Dependencies
  • bpo-10371: Deprecate trace module undocumented API
    		•
    Files
  • testtrace.zip: run as "python testtrace.zip"
  • issue10342.diff
  • issue10342a.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 = 'https://github.com/abalkin'
closed_at = None
created_at = <Date 2010-11-06.15:26:46.239>
labels = ['3.7', 'type-bug', 'library']
title = 'trace module cannot produce coverage reports for zipped modules'
updated_at = <Date 2016-09-10.18:41:24.390>
user = 'https://github.com/abalkin'

    bugs.python.org fields:

    activity = <Date 2016-09-10.18:41:24.390>
actor = 'belopolsky'
assignee = 'belopolsky'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-11-06.15:26:46.239>
creator = 'belopolsky'
dependencies = ['10371']
files = ['19522', '19537', '35803']
hgrepos = []
issue_num = 10342
keywords = ['patch', 'needs review']
message_count = 12.0
messages = ['120626', '120691', '120701', '120703', '120704', '120707', '120708', '121051', '121056', '121067', '221928', '221944']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'belopolsky', 'vstinner', 'Claudiu.Popa']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10342'
versions = ['Python 3.7']

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.