Tracing not disabled in generator when the system trace function returns None.

Open
#64,239 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

The issue links the uploaded tracer.py file and concerns interpreter-core generator tracing. Start by reading tracer.py and locating the generator tracing path, then reproduce the case where the system trace function returns None. Done means tracing is disabled for the generator in that case, with regression coverage added in the relevant test suite.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 20040
Nosy @pitrou, @nedbat, @xdegaye, @serhiy-storchaka
Files
  • tracer.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 2013-12-21.13:55:53.784>
labels = ['interpreter-core', 'type-bug']
title = 'Tracing not disabled in generator when the system trace function returns None.'
updated_at = <Date 2013-12-21.14:21:32.455>
user = 'https://github.com/xdegaye'

    bugs.python.org fields:

    activity = <Date 2013-12-21.14:21:32.455>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-12-21.13:55:53.784>
creator = 'xdegaye'
dependencies = []
files = ['33244']
hgrepos = []
issue_num = 20040
keywords = []
message_count = 2.0
messages = ['206734', '206738']
nosy_count = 4.0
nosy_names = ['pitrou', 'nedbat', 'xdegaye', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20040'
versions = ['Python 3.4']

    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.