signal.default_int_handler should set signal number on the raised exception

Open
#61,384 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the signal.default_int_handler entry point and inspect the surrounding signal-handling implementation. Done means the exception raised by the handler includes the signal number requested by the issue; the payload does not identify a file or test.

Written by the indexing model from the issue text.

Description

extension-modules type-feature
BPO 17182
Nosy @pitrou, @matrixise

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-02-11.13:59:50.914>
labels = ['extension-modules', 'type-feature']
title = 'signal.default_int_handler should set signal number on the raised exception'
updated_at = <Date 2016-10-13.19:27:50.893>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2016-10-13.19:27:50.893>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2013-02-11.13:59:50.914>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 17182
keywords = []
message_count = 4.0
messages = ['181894', '223375', '278564', '278565']
nosy_count = 2.0
nosy_names = ['pitrou', 'matrixise']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17182'
versions = ['Python 3.5']

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.