Callers of _Py_fopen/_Py_wfopen may be broken after addition of audit hooks
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42569 |
|---|---|
| Nosy | @vstinner, @eryksun, @zooba, @izbyshev |
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 2020-12-04.16:12:33.309>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9', '3.10']
title = 'Callers of _Py_fopen/_Py_wfopen may be broken after addition of audit hooks'
updated_at = <Date 2020-12-09.00:22:36.566>
user = 'https://github.com/izbyshev'
bugs.python.org fields:
activity = <Date 2020-12-09.00:22:36.566>
actor = 'izbyshev'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-12-04.16:12:33.309>
creator = 'izbyshev'
dependencies = []
files = []
hgrepos = []
issue_num = 42569
keywords = []
message_count = 11.0
messages = ['382499', '382507', '382508', '382513', '382521', '382540', '382549', '382589', '382658', '382777', '382779']
nosy_count = 4.0
nosy_names = ['vstinner', 'eryksun', 'steve.dower', 'izbyshev']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42569'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
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 by tracing the callers of _Py_fopen and _Py_wfopen and reviewing how audit hooks affect those entry points. The issue does not name files or tests; done means identifying and correcting any caller breakage, with coverage for the affected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100