pthread_sigmask needs SIG_BLOCK behaviour explaination
Open
Nobody has claimed this yet.
3.10
3.11
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47139 |
|---|---|
| Nosy | @gpshead, @rpurdie |
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 2022-03-28.09:48:02.840>
labels = ['interpreter-core', 'type-bug', '3.10', '3.11']
title = 'pthread_sigmask needs SIG_BLOCK behaviour explaination'
updated_at = <Date 2022-04-05.19:28:09.388>
user = 'https://github.com/rpurdie'
bugs.python.org fields:
activity = <Date 2022-04-05.19:28:09.388>
actor = 'rpurdie'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2022-03-28.09:48:02.840>
creator = 'rpurdie'
dependencies = []
files = []
hgrepos = []
issue_num = 47139
keywords = []
message_count = 4.0
messages = ['416154', '416757', '416794', '416808']
nosy_count = 2.0
nosy_names = ['gregory.p.smith', 'rpurdie']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue47139'
versions = ['Python 3.10', '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 at the pthread_sigmask entry point in Python's signal documentation and review how SIG_BLOCK is currently described. Clarify the SIG_BLOCK behavior, then verify the resulting documentation with the relevant documentation build or checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100