PEP 526
E911262
PEP 526 is a Python Enhancement Proposal that introduced a standard syntax for variable and attribute type annotations in Python.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 526 canonical | 7 |
How this entity was disambiguated
This entity first appeared as the object of triple T11216058 — 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 526 Context triple: [PEP 484, relatedTo, PEP 526]
-
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 578
PEP 578 is a Python enhancement proposal that introduces a security audit hook framework to help monitor and control runtime events in Python applications.
-
D.
PEP 590
PEP 590 is the Python Enhancement Proposal that introduced the "vectorcall" protocol to speed up and standardize function calls in CPython.
-
E.
PEP 626
PEP 626 is a Python Enhancement Proposal that precisely defines how Python should map executed bytecode instructions to source code lines, improving debugging, coverage measurement, and tooling accuracy.
- 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 526 Target entity description: PEP 526 is a Python Enhancement Proposal that introduced a standard syntax for variable and attribute type annotations in Python.
-
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 578
PEP 578 is a Python enhancement proposal that introduces a security audit hook framework to help monitor and control runtime events in Python applications.
-
D.
PEP 590
PEP 590 is the Python Enhancement Proposal that introduced the "vectorcall" protocol to speed up and standardize function calls in CPython.
-
E.
PEP 626
PEP 626 is a Python Enhancement Proposal that precisely defines how Python should map executed bytecode instructions to source code lines, improving debugging, coverage measurement, and tooling accuracy.
- F. None of above. chosen
Statements (35)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| affects | static type checking in Python ⓘ |
| allows |
annotations for class attributes
ⓘ
annotations for instance attributes ⓘ annotations for module-level variables ⓘ |
| author |
Guido van Rossum
ⓘ
Jukka Lehtosalo ⓘ Łukasz Langa ⓘ |
| bdflDelegate | Guido van Rossum ⓘ |
| category | Typing ⓘ |
| clarifies | that annotations have no runtime effect by default ⓘ |
| created | 2016-09-07 ⓘ |
| defines |
syntax for attribute annotations
ⓘ
syntax for variable annotations ⓘ |
| discussedOn | python-dev mailing list ⓘ |
| exampleSyntax |
primes: List[int] = []
ⓘ
self.name: str ⓘ x: int = 0 ⓘ |
| influenced | subsequent typing-related PEPs ⓘ |
| introducedInPythonVersion | Python 3.6 ⓘ |
| language | Python ⓘ |
| motivation | standardize syntax for type annotations on variables and attributes ⓘ |
| number | 526 ⓘ |
| relatedTo |
PEP 3107
ⓘ
PEP 484 ⓘ |
| replaces | comment-based type hints for variables ⓘ |
| requires | support from type checkers like mypy ⓘ |
| scope | syntax only, not type system semantics ⓘ |
| specifies | storage of annotations in __annotations__ mapping ⓘ |
| status | Final ⓘ |
| title | Syntax for Variable Annotations ⓘ |
| topic |
attribute annotations
ⓘ
type annotations ⓘ variable annotations ⓘ |
| url | https://peps.python.org/pep-0526/ ⓘ |
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 526 Description of subject: PEP 526 is a Python Enhancement Proposal that introduced a standard syntax for variable and attribute type annotations in Python.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
typing
subject linked to:
Python typing module