Early auditing broken
Open
Nobody has claimed this yet.
3.10
3.11
3.12
3.13
3.9 (EOL)
interpreter-core
type-bug
type-security
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37505 |
|---|---|
| Nosy | @vstinner, @tiran, @zooba |
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-07-05.12:07:59.201>
labels = ['type-security', 'interpreter-core', '3.9', '3.10', '3.11']
title = 'Early auditing broken'
updated_at = <Date 2021-10-20.16:18:20.519>
user = 'https://github.com/tiran'
bugs.python.org fields:
activity = <Date 2021-10-20.16:18:20.519>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-07-05.12:07:59.201>
creator = 'christian.heimes'
dependencies = []
files = []
hgrepos = []
issue_num = 37505
keywords = []
message_count = 9.0
messages = ['347334', '347344', '347345', '347353', '347357', '347358', '347360', '347536', '347538']
nosy_count = 3.0
nosy_names = ['vstinner', 'christian.heimes', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'security'
url = 'https://bugs.python.org/issue37505'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 reading the linked bugs.python.org issue 37505 and its discussion, then inspect the Python interpreter-core auditing implementation. The payload does not name a source file, test, reproduction, or expected behavior, so the affected entry point and completion criteria still need to be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100