python / python/cpython

destructors of local variables are not traced

Open
#77,627 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) 3.8 (EOL) interpreter-core stdlib type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Description

BPO 33446
Nosy @xdegaye, @serhiy-storchaka
PRs
  • python/cpython#6730
  • 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 2018-05-08.18:29:15.715>
    labels = ['interpreter-core', '3.8', 'type-bug', 'library', '3.7']
    title = 'destructors of local variables are not traced'
    updated_at = <Date 2018-05-08.19:00:03.664>
    user = 'https://github.com/xdegaye'
    

    bugs.python.org fields:

    activity = <Date 2018-05-08.19:00:03.664>
    actor = 'serhiy.storchaka'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core', 'Library (Lib)']
    creation = <Date 2018-05-08.18:29:15.715>
    creator = 'xdegaye'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 33446
    keywords = ['patch']
    message_count = 2.0
    messages = ['316290', '316292']
    nosy_count = 2.0
    nosy_names = ['xdegaye', 'serhiy.storchaka']
    pr_nums = ['6730']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue33446'
    versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
    

    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.

    Research direction

    Start by reviewing the issue's referenced PR #6730 and the CPython interpreter-core changes it discusses. Done would mean resolving the reported destructor-tracing behavior and validating it with the relevant interpreter tests, though no test file or entry point is named here.

    Written by the indexing model from the issue text.

    Assessment

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

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.