trace module cannot produce coverage reports for zipped modules

Open
#54,551 12 comments 0 reactions 1 assignee View on GitHub

@abalkin is already working on this.

Since Nov 6, 2010.

Assessment

This issue has not been assessed yet.

Description

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

    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.