PEP 518
E1274579
UNEXPLORED
PEP 518 is a Python Enhancement Proposal that defines how Python projects specify their build system requirements using a `pyproject.toml` configuration file.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 518 canonical | 7 |
How this entity was disambiguated
This entity first appeared as the object of triple T17522078 — 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 518 Context triple: [installer (PyPA project), conformsTo, PEP 518]
-
A.
PEP 517
PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
-
B.
PEP 508
PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
-
C.
PEP 552
PEP 552 is a Python Enhancement Proposal that introduced deterministic, hash-based .pyc files to improve reproducibility and caching behavior in Python.
-
D.
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.
-
E.
PEP 544
PEP 544 is a Python Enhancement Proposal that introduces structural subtyping via typing.Protocol, enabling static type checkers to support interface-like behavior based on object capabilities rather than inheritance.
- 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 518 Target entity description: PEP 518 is a Python Enhancement Proposal that defines how Python projects specify their build system requirements using a `pyproject.toml` configuration file.
-
A.
PEP 517
PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
-
B.
PEP 508
PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
-
C.
PEP 552
PEP 552 is a Python Enhancement Proposal that introduced deterministic, hash-based .pyc files to improve reproducibility and caching behavior in Python.
-
D.
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.
-
E.
PEP 544
PEP 544 is a Python Enhancement Proposal that introduces structural subtyping via typing.Protocol, enabling static type checkers to support interface-like behavior based on object capabilities rather than inheritance.
- F. None of above. chosen
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
PEP 517 (via backends)
subject linked to:
PEP 621 (project metadata in pyproject.toml, partially)