Add pid to .cover filename in lib/trace.py

Open
#76,333 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reading lib/trace.py and locate where .cover filenames are constructed. Check the linked trace_generic.py reference for the intended behavior, then confirm that generated .cover filenames include the process ID without breaking the existing trace output.

Written by the indexing model from the issue text.

Description

3.7 (EOL) 3.8 (EOL) stdlib type-feature
BPO 32152
Nosy @nedbat, @nikhilh-20
Files
  • trace_generic.py
    		•

    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 2017-11-28.08:45:04.422>
labels = ['3.7', '3.8', 'type-feature', 'library']
title = 'Add pid to .cover filename in lib/trace.py'
updated_at = <Date 2018-09-16.13:13:55.329>
user = 'https://github.com/nikhilh-20'

    bugs.python.org fields:

    activity = <Date 2018-09-16.13:13:55.329>
actor = 'nedbat'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-11-28.08:45:04.422>
creator = 'nikhilh'
dependencies = []
files = ['47300']
hgrepos = []
issue_num = 32152
keywords = []
message_count = 5.0
messages = ['307110', '307112', '307388', '308499', '325483']
nosy_count = 2.0
nosy_names = ['nedbat', 'nikhilh']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32152'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8']

    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.