PEP 426
E1281691
UNEXPLORED
PEP 426 was a proposed Python Enhancement Proposal that aimed to standardize a new metadata format for Python packages but was ultimately superseded before full adoption.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 426 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T17522265 — 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 426 Context triple: [PEP 508, replaces, PEP 426]
-
A.
PEP 425
PEP 425 is a Python Enhancement Proposal that defines the standardized “compatibility tag” scheme used to identify which Python interpreter and platform a binary distribution (like a wheel) is compatible with.
-
B.
PEP 427
PEP 427 is the Python Enhancement Proposal that defines the Wheel binary package format used for distributing and installing Python projects.
-
C.
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.
-
D.
PEP 624
PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
-
E.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
- 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 426 Target entity description: PEP 426 was a proposed Python Enhancement Proposal that aimed to standardize a new metadata format for Python packages but was ultimately superseded before full adoption.
-
A.
PEP 425
PEP 425 is a Python Enhancement Proposal that defines the standardized “compatibility tag” scheme used to identify which Python interpreter and platform a binary distribution (like a wheel) is compatible with.
-
B.
PEP 427
PEP 427 is the Python Enhancement Proposal that defines the Wheel binary package format used for distributing and installing Python projects.
-
C.
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.
-
D.
PEP 624
PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
-
E.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
- F. None of above. chosen
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.