PEP 578
E895952
PEP 578 is a Python enhancement proposal that introduces a security audit hook framework to help monitor and control runtime events in Python applications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 578 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10851816 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEP 578 Context triple: [Python 3.8, hasPEP, PEP 578]
-
A.
PEP 570
PEP 570 is the Python Enhancement Proposal that introduced positional-only parameters to Python function definitions, formalizing a syntax for arguments that must be passed by position.
-
B.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
C.
PEP 695
PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
-
D.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
E.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PEP 578 Target entity description: PEP 578 is a Python enhancement proposal that introduces a security audit hook framework to help monitor and control runtime events in Python applications.
-
A.
PEP 570
PEP 570 is the Python Enhancement Proposal that introduced positional-only parameters to Python function definitions, formalizing a syntax for arguments that must be passed by position.
-
B.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
C.
PEP 695
PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
-
D.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
E.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| aimsTo |
help control runtime events in Python applications
ⓘ
help monitor runtime events in Python applications ⓘ |
| allows |
interception of selected runtime events
ⓘ
registration of audit hooks at runtime ⓘ |
| appliesTo |
Python runtime
ⓘ
Python standard library NERFINISHED ⓘ |
| belongsToCategory | Security PEP NERFINISHED ⓘ |
| clarifies | how and when audit hooks are invoked ⓘ |
| createdForVersion | Python 3.8 NERFINISHED ⓘ |
| definesAPI |
audit hooks
ⓘ
sys.addaudithook ⓘ |
| definesConcept |
audit events
ⓘ
audit hook callbacks ⓘ |
| discussedOn | python-dev mailing list NERFINISHED ⓘ |
| documentType | design specification ⓘ |
| enables |
integration with external security monitoring systems
ⓘ
system-wide auditing of Python code execution ⓘ |
| ensures | backwards compatibility where possible ⓘ |
| focusesOn |
auditing
ⓘ
security ⓘ |
| governingBody | Python Software Foundation NERFINISHED ⓘ |
| hasAuthor | Steve Dower NERFINISHED ⓘ |
| implementedIn | CPython NERFINISHED ⓘ |
| introducesFeature |
Python runtime audit hooks
ⓘ
security audit hook framework ⓘ |
| language | English ⓘ |
| motivation |
enable external tools to audit Python runtime behavior
ⓘ
provide a standardized way to observe security-relevant events ⓘ |
| partOf | Python language specification process ⓘ |
| relatedTo |
PEP 551
NERFINISHED
ⓘ
Python security model ⓘ |
| repository | https://peps.python.org/pep-0578/ ⓘ |
| scope | CPython interpreter behavior ⓘ |
| status | Final ⓘ |
| targetAudience |
Python implementers
ⓘ
library and framework authors ⓘ security engineers ⓘ |
| title | PEP 578 – Python Runtime Audit Hooks NERFINISHED ⓘ |
| type | Standards Track PEP NERFINISHED ⓘ |
| yearProposed | 2019 ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: PEP 578 Description of subject: PEP 578 is a Python enhancement proposal that introduces a security audit hook framework to help monitor and control runtime events in Python applications.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.