sys.addaudithook(hook) loops indefinitely on mismatch for hook
Open
Nobody has claimed this yet.
3.12
3.13
3.14
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39182 |
|---|---|
| Nosy | @terryjreedy, @tiran, @zooba, @Dutcho |
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-01-01.17:23:00.844>
labels = ['type-bug', '3.8', '3.9']
title = 'sys.addaudithook(hook) loops indefinitely on mismatch for hook'
updated_at = <Date 2020-01-04.19:40:23.157>
user = 'https://github.com/Dutcho'
bugs.python.org fields:
activity = <Date 2020-01-04.19:40:23.157>
actor = 'steve.dower'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-01-01.17:23:00.844>
creator = 'Dutcho'
dependencies = []
files = []
hgrepos = []
issue_num = 39182
keywords = []
message_count = 5.0
messages = ['359164', '359247', '359279', '359280', '359307']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'christian.heimes', 'steve.dower', 'Dutcho']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39182'
versions = ['Python 3.8', 'Python 3.9']
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 at the sys.addaudithook(hook) entry point and reproduce the mismatch case described in the issue. Trace where the hook comparison is handled, then confirm that the mismatch terminates rather than looping indefinitely and add a regression test for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100