PEP 660
E1276850
UNEXPLORED
PEP 660 is a Python packaging standard that defines how editable installs should work for PEP 517 build backends, enabling consistent development workflows across tools.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 660 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T17522079 — 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 660 Context triple: [installer (PyPA project), conformsTo, PEP 660]
-
A.
PEP 685
PEP 685 is a Python Enhancement Proposal that introduces a standard for handling and normalizing direct URL references in Python package metadata to improve interoperability across packaging tools.
-
B.
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.
-
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 657
PEP 657 is a Python enhancement proposal that improves error reporting by adding fine-grained location information (such as per-expression line and column data) to tracebacks.
-
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 660 Target entity description: PEP 660 is a Python packaging standard that defines how editable installs should work for PEP 517 build backends, enabling consistent development workflows across tools.
-
A.
PEP 685
PEP 685 is a Python Enhancement Proposal that introduces a standard for handling and normalizing direct URL references in Python package metadata to improve interoperability across packaging tools.
-
B.
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.
-
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 657
PEP 657 is a Python enhancement proposal that improves error reporting by adding fine-grained location information (such as per-expression line and column data) to tracebacks.
-
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
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
PEP 518 (pyproject.toml build-system)