PEP 695
E52336
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.
All labels observed (2)
| Label | Occurrences |
|---|---|
| PEP 695 canonical | 7 |
| PEP 695: Type Parameter Syntax | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T400419 — 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 695 Context triple: [Python Enhancement Proposals, hasPart, PEP 695]
-
A.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
B.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
C.
PEP 0
PEP 0 is the index document that lists and tracks the status of all Python Enhancement Proposals (PEPs) in the Python community.
-
D.
Python Enhancement Proposals
Python Enhancement Proposals (PEPs) are the formal design documents that propose, specify, and document new features, processes, and standards for the Python programming language.
-
E.
PEP 1
PEP 1 is the foundational Python Enhancement Proposal that defines the purpose, structure, and workflow for all other PEPs in the Python community process.
- 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 695 Target entity description: 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.
-
A.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
B.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
C.
PEP 0
PEP 0 is the index document that lists and tracks the status of all Python Enhancement Proposals (PEPs) in the Python community.
-
D.
Python Enhancement Proposals
Python Enhancement Proposals (PEPs) are the formal design documents that propose, specify, and document new features, processes, and standards for the Python programming language.
-
E.
PEP 1
PEP 1 is the foundational Python Enhancement Proposal that defines the purpose, structure, and workflow for all other PEPs in the Python community process.
- F. None of above. chosen
Statements (34)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| affects |
Python generic class definitions
ⓘ
Python generic function definitions ⓘ Python type checkers ⓘ |
| aimsTo |
improve static typing in Python
ⓘ
improve support for generics in Python ⓘ |
| belongsTo |
Python type system
ⓘ
Python typing ecosystem ⓘ
linked to:
Pydantic
|
| category | Typing ⓘ |
| defines |
syntax for declaring type parameters on classes
ⓘ
syntax for declaring type parameters on functions ⓘ syntax for declaring type parameters on type aliases ⓘ |
| documentationURL | https://peps.python.org/pep-0695/ ⓘ |
| focusesOn | type parameter declarations ⓘ |
| governs | how type parameters are declared in source code ⓘ |
| hasTitle | Type Parameter Syntax ⓘ |
| improves |
ergonomics of static typing in Python
ⓘ
readability of generic type declarations ⓘ |
| intendedFor |
Python application developers
ⓘ
Python library authors ⓘ static type checker implementers ⓘ |
| introduces | more concise syntax for type parameters ⓘ |
| language | Python ⓘ |
| motivatedBy |
need for clearer generic APIs
ⓘ
verbosity of existing typing.Generic-based syntax ⓘ |
| number | 695 ⓘ |
| proposes | new syntax for type parameter declarations in Python ⓘ |
| relatedTo |
PEP 484
ⓘ
PEP 585 ⓘ Python typing module ⓘ
linked to:
Python standard library
|
| scope |
generic programming in Python
ⓘ
static type checking ⓘ |
| status | Accepted ⓘ |
| targets | Python generic types ⓘ |
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 695 Description of subject: 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.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: PEP 695