_posixsubprocess.c: sysconf() might not be async-signal-safe

Open
#69,112 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
operating-systems

Research direction

Start by reading _posixsubprocess.c and locating the sysconf() call mentioned in the title. Investigate the async-signal-safety requirements for that call and the surrounding subprocess path; the issue does not specify a test, replacement, or exact completion criteria, so confirm the intended fix with project maintainers before proceeding.

Written by the indexing model from the issue text.

Description

extension-modules
BPO 24924
Nosy @gpshead, @jwilk

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-08-24.15:25:11.839>
labels = ['extension-modules']
title = '_posixsubprocess.c: sysconf() might not be async-signal-safe'
updated_at = <Date 2015-08-24.16:24:01.802>
user = 'https://github.com/jwilk'

bugs.python.org fields:

activity = <Date 2015-08-24.16:24:01.802>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2015-08-24.15:25:11.839>
creator = 'jwilk'
dependencies = []
files = []
hgrepos = []
issue_num = 24924
keywords = []
message_count = 1.0
messages = ['249058']
nosy_count = 2.0
nosy_names = ['gregory.p.smith', 'jwilk']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24924'
versions = []

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.