PEP 3107
E911261
PEP 3107 is the Python Enhancement Proposal that introduced function annotations, providing a standardized syntax for attaching metadata such as type information to function parameters and return values.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 3107 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T11216056 — 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 3107 Context triple: [PEP 484, relatedTo, PEP 3107]
-
A.
PEP 333
PEP 333 is the Python Enhancement Proposal that originally defined the Web Server Gateway Interface (WSGI), a standard for communication between Python web applications and web servers.
-
B.
PEP 613
PEP 613 is a Python Enhancement Proposal that introduces the `TypeAlias` annotation to clearly declare and distinguish type aliases in Python’s type hinting system.
-
C.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
D.
PEP 612
PEP 612 is a Python Enhancement Proposal that introduces support for parameter specification variables to improve typing of higher-order functions and decorators in Python’s type system.
-
E.
PEP 618
PEP 618 is a Python Enhancement Proposal that introduced the `strict` parameter to the built-in `zip` function, enabling stricter handling of iterables with mismatched lengths.
- 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 3107 Target entity description: PEP 3107 is the Python Enhancement Proposal that introduced function annotations, providing a standardized syntax for attaching metadata such as type information to function parameters and return values.
-
A.
PEP 333
PEP 333 is the Python Enhancement Proposal that originally defined the Web Server Gateway Interface (WSGI), a standard for communication between Python web applications and web servers.
-
B.
PEP 613
PEP 613 is a Python Enhancement Proposal that introduces the `TypeAlias` annotation to clearly declare and distinguish type aliases in Python’s type hinting system.
-
C.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
D.
PEP 612
PEP 612 is a Python Enhancement Proposal that introduces support for parameter specification variables to improve typing of higher-order functions and decorators in Python’s type system.
-
E.
PEP 618
PEP 618 is a Python Enhancement Proposal that introduced the `strict` parameter to the built-in `zip` function, enabling stricter handling of iterables with mismatched lengths.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| acceptedBy | Python core developers ⓘ |
| allows | any Python expression as an annotation ⓘ |
| annotationStorage | __annotations__ attribute on functions ⓘ |
| author | Guido van Rossum ⓘ |
| backwardsCompatibility | does not change function call semantics ⓘ |
| created | 2006-03-05 ⓘ |
| defines |
syntax for attaching metadata to function parameters
ⓘ
syntax for attaching metadata to function return values ⓘ |
| designGoal |
allow arbitrary metadata on function parameters
ⓘ
avoid enforcing a specific type system ⓘ keep annotations optional ⓘ |
| doesNotSpecify | how tools should interpret annotations ⓘ |
| implementedInVersion |
Python 3.0
ⓘ
linked to:
Python 3.x
|
| influenced |
PEP 484
ⓘ
Python type hinting ecosystem ⓘ |
| introducedFeature | function annotations ⓘ |
| introducedSyntax |
parameter annotations
ⓘ
return value annotations ⓘ |
| language | Python ⓘ |
| metadataKind |
documentation metadata
ⓘ
type information ⓘ validation metadata ⓘ |
| motivatedBy | need for standardized way to attach metadata to functions ⓘ |
| primaryUseCase |
documentation
ⓘ
static analysis ⓘ type information ⓘ |
| proposalNumber | 3107 ⓘ |
| pythonVersionIntroduced |
Python 3.0
ⓘ
linked to:
Python 3.x
|
| relatedTo |
PEP 484
ⓘ
PEP 526 ⓘ PEP 563 ⓘ PEP 649 ⓘ |
| replaces | earlier informal annotation proposals ⓘ |
| scope |
function definitions
ⓘ
method definitions ⓘ |
| semantics |
annotations are available for introspection
ⓘ
annotations have no runtime effect by default ⓘ |
| status | Final ⓘ |
| syntaxExample | def f(x: int) -> str: ... ⓘ |
| targetAudience | Python developers ⓘ |
| title | Function Annotations ⓘ |
| type | Standards Track ⓘ |
| url | https://peps.python.org/pep-3107/ ⓘ |
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 3107 Description of subject: PEP 3107 is the Python Enhancement Proposal that introduced function annotations, providing a standardized syntax for attaching metadata such as type information to function parameters and return values.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.