python / python/cpython

why call _Py_set_inheritable(0) from os.open() when O_CLOEXEC?

Open
#80,796 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

BPO 36615
Nosy @vstinner, @cagney

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.14:46:33.267>
labels = ['3.8']
title = 'why call _Py_set_inheritable(0) from os.open() when O_CLOEXEC?'
updated_at = <Date 2019-04-12.14:50:18.302>
user = 'https://github.com/cagney'

bugs.python.org fields:

activity = <Date 2019-04-12.14:50:18.302>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-04-12.14:46:33.267>
creator = 'cagney'
dependencies = []
files = []
hgrepos = []
issue_num = 36615
keywords = []
message_count = 2.0
messages = ['340050', '340051']
nosy_count = 2.0
nosy_names = ['vstinner', 'cagney']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36615'
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

Start by tracing os.open and _Py_set_inheritable when O_CLOEXEC is used, then review the linked BPO discussion and its two messages. Determine whether the call is redundant or required on supported platforms, and document the decision with any needed test coverage.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.