Modules/signalmodule.c creates handlers for signals bounded by `NSIG`; requires fudging to support realtime signals, etc
Open
Nobody has claimed this yet.
3.8 (EOL)
interpreter-core
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39565 |
|---|---|
| Nosy | @ngie-eign |
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 2020-02-05.22:15:07.671>
labels = ['interpreter-core', '3.8']
title = 'Modules/signalmodule.c creates handlers for signals bounded by `NSIG`; requires fudging to support realtime signals, etc'
updated_at = <Date 2020-02-06.17:48:15.443>
user = 'https://github.com/ngie-eign'
bugs.python.org fields:
activity = <Date 2020-02-06.17:48:15.443>
actor = 'ngie'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-02-05.22:15:07.671>
creator = 'ngie'
dependencies = []
files = []
hgrepos = []
issue_num = 39565
keywords = []
message_count = 1.0
messages = ['361458']
nosy_count = 1.0
nosy_names = ['ngie']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39565'
versions = ['Python 3.8']
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 in Modules/signalmodule.c by tracing how signal handlers are created and how NSIG bounds supported signals. Done means defining and implementing a clear way for the module to support realtime signals and related cases, with corresponding signal-handling coverage identified during the investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100