python / python/cpython

when is os.posix_spawn(setsid=True) safe?

Open
#80,800 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.8 (EOL) type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 36619
Nosy @vstinner, @methane, @serhiy-storchaka, @cagney, @pablogsal, @nanjekyejoannah

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 2019-04-12.17:58:10.185>
labels = ['type-feature', '3.8', 'expert-IO']
title = 'when is os.posix_spawn(setsid=True) safe?'
updated_at = <Date 2019-04-15.09:42:02.043>
user = 'https://github.com/cagney'

bugs.python.org fields:

activity = <Date 2019-04-15.09:42:02.043>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2019-04-12.17:58:10.185>
creator = 'cagney'
dependencies = []
files = []
hgrepos = []
issue_num = 36619
keywords = []
message_count = 3.0
messages = ['340091', '340248', '340249']
nosy_count = 6.0
nosy_names = ['vstinner', 'methane', 'serhiy.storchaka', 'cagney', 'pablogsal', 'nanjekyejoannah']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue36619'
versions = ['Python 3.8']

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.

Research direction

The issue concerns os.posix_spawn(setsid=True), but it names no files, tests, or concrete change. Start by reading the existing os.posix_spawn entry point and the linked BPO discussion; determine what safety guidance or behavior is required, then capture the agreed outcome in tests or documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.