_Py_open does not work with O_CREAT

Open
#64,627 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the _Py_open entry point in CPython and reproduce the O_CREAT case described in the issue. Trace the existing behavior and add regression coverage; done means _Py_open works correctly when O_CREAT is used.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 20428
Nosy @vstinner, @avassalotti

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 2014-01-28.23:45:30.731>
labels = ['interpreter-core', 'type-bug']
title = '_Py_open does not work with O_CREAT'
updated_at = <Date 2014-02-03.01:14:35.281>
user = 'https://github.com/avassalotti'

bugs.python.org fields:

activity = <Date 2014-02-03.01:14:35.281>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-01-28.23:45:30.731>
creator = 'alexandre.vassalotti'
dependencies = []
files = []
hgrepos = []
issue_num = 20428
keywords = []
message_count = 4.0
messages = ['209600', '209602', '209609', '210066']
nosy_count = 2.0
nosy_names = ['vstinner', 'alexandre.vassalotti']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20428'
versions = ['Python 3.4']

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.