python / python/cpython

Make CHECK_STATUS_PTHREAD signal-safe

Open
#74,951 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) interpreter-core type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 30766
Nosy @pitrou, @methane
PRs
  • python/cpython#2404
  • 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-06-26.12:40:49.115>
    labels = ['interpreter-core', 'type-bug', '3.7']
    title = 'Make CHECK_STATUS_PTHREAD signal-safe'
    updated_at = <Date 2019-03-06.10:15:32.016>
    user = 'https://github.com/pitrou'
    

    bugs.python.org fields:

    activity = <Date 2019-03-06.10:15:32.016>
    actor = 'methane'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2017-06-26.12:40:49.115>
    creator = 'pitrou'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 30766
    keywords = []
    message_count = 2.0
    messages = ['296887', '337288']
    nosy_count = 2.0
    nosy_names = ['pitrou', 'methane']
    pr_nums = ['2404']
    priority = 'low'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue30766'
    versions = ['Python 3.5', 'Python 3.6', 'Python 3.7']
    

    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 PR #2404 and locating CHECK_STATUS_PTHREAD in the interpreter core. Use the issue and PR context to determine the required signal-safe behavior; done means that behavior is implemented and the issue is resolved.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    operating-systems
    Issue type
    Bug
    Difficulty
    4/5
    Estimated time
    3-5 days
    Activity status
    Stale
    Clarity
    Mostly clear
    Newbie friendliness
    25/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.