Doc: signal.sig(timed)wait do not work outside the main thread
Open
Nobody has claimed this yet.
3.11
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29374 |
|---|---|
| Nosy | @vadmium, @petr-motejlek |
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 2017-01-25.17:25:31.331>
labels = ['3.11', 'type-feature', 'docs']
title = 'Doc: signal.sig(timed)wait do not work outside the main thread'
updated_at = <Date 2021-10-22.10:01:01.554>
user = 'https://github.com/petr-motejlek'
bugs.python.org fields:
activity = <Date 2021-10-22.10:01:01.554>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-01-25.17:25:31.331>
creator = 'petr@motejlek.net'
dependencies = []
files = []
hgrepos = []
issue_num = 29374
keywords = []
message_count = 2.0
messages = ['286269', '286284']
nosy_count = 3.0
nosy_names = ['docs@python', 'martin.panter', 'petr@motejlek.net']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue29374'
versions = ['Python 3.11']
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 the documentation for signal.sigwait and signal.sigtimedwait and check how their thread restrictions are currently described. Done means the signal documentation clearly states their behavior outside the main thread; the payload names no specific documentation file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100