signal handler never gets called

Open
#49,565 9 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
operating-systems

Research direction

Start by running tsig.py, the script attached to the issue, to reproduce the signal behavior. Then read select_select.diff and the issue history to understand the proposed context; no current test or acceptance criterion is named, so confirm the expected behavior with maintainers before changing code.

Written by the indexing model from the issue text.

Description

docs interpreter-core stdlib type-bug
BPO 5315
Nosy @tim-one, @birkenfeld, @terryjreedy, @pitrou, @vstinner, @ssbr
Files
  • tsig.py: Python script which triggers the strange behavior
  • select_select.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 = None
closed_at = None
created_at = <Date 2009-02-19.13:47:06.207>
labels = ['interpreter-core', 'type-bug', 'library', 'docs']
title = 'signal handler never gets called'
updated_at = <Date 2018-03-29.20:05:00.027>
user = 'https://bugs.python.org/pts'

    bugs.python.org fields:

    activity = <Date 2018-03-29.20:05:00.027>
actor = 'Patrick Fink'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Interpreter Core', 'Library (Lib)']
creation = <Date 2009-02-19.13:47:06.207>
creator = 'pts'
dependencies = []
files = ['13138', '39489']
hgrepos = []
issue_num = 5315
keywords = ['patch']
message_count = 9.0
messages = ['82472', '100306', '100309', '102829', '102850', '244015', '244019', '246963', '314669']
nosy_count = 12.0
nosy_names = ['tim.peters', 'georg.brandl', 'terry.reedy', 'pitrou', 'amcnabb', 'vstinner', 'Devin Jeanpierre', 'pts', 's7v7nislands', 'neologix', 'Netto', 'Patrick Fink']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue5315'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

    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.