signalmodule.c does "is" comparisons for SIG_IGN and SIG_DFL
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28069 |
|---|---|
| Nosy | @mdickinson, @berkerpeksag, @serhiy-storchaka |
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 2016-09-10.19:49:19.914>
labels = ['type-bug', 'library']
title = 'signalmodule.c does "is" comparisons for SIG_IGN and SIG_DFL'
updated_at = <Date 2018-08-23.23:54:00.666>
user = 'https://github.com/mdickinson'
bugs.python.org fields:
activity = <Date 2018-08-23.23:54:00.666>
actor = 'berker.peksag'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-09-10.19:49:19.914>
creator = 'mark.dickinson'
dependencies = []
files = []
hgrepos = []
issue_num = 28069
keywords = []
message_count = 3.0
messages = ['275687', '275688', '275696']
nosy_count = 3.0
nosy_names = ['mark.dickinson', 'berker.peksag', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue28069'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading signalmodule.c and locate the comparisons involving SIG_IGN and SIG_DFL. Trace the surrounding signal-handling behavior, then verify that the comparisons use the intended semantics and preserve existing behavior; the payload does not name a regression test, so identify the relevant signal tests before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100