signal.set_wakeup_fd() doesn't work if the signal don't have handler

Open
#69,668 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
28/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the documentation for signal.set_wakeup_fd() and the historical discussion linked in the issue. Determine what behavior should be documented when a signal has no handler; done means the documentation clearly explains the expected behavior and any relevant limitation.

Written by the indexing model from the issue text.

Description

docs
BPO 25482
Nosy @atsuoishimoto, @vstinner, @benjaminp

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 2015-10-26.11:34:56.021>
labels = ['docs']
title = "signal.set_wakeup_fd() doesn't work if the signal don't have handler"
updated_at = <Date 2015-10-30.11:39:35.835>
user = 'https://github.com/atsuoishimoto'

bugs.python.org fields:

activity = <Date 2015-10-30.11:39:35.835>
actor = 'ishimoto'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-10-26.11:34:56.021>
creator = 'ishimoto'
dependencies = []
files = []
hgrepos = []
issue_num = 25482
keywords = []
message_count = 12.0
messages = ['253468', '253517', '253520', '253602', '253657', '253677', '253711', '253712', '253724', '253727', '253728', '253729']
nosy_count = 4.0
nosy_names = ['ishimoto', 'vstinner', 'benjamin.peterson', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue25482'
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.