PEP 517
E427614
PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
All labels observed (3)
| Label | Occurrences |
|---|---|
| PEP 517 canonical | 7 |
| PEP 517 – A build-system independent format for source trees | 1 |
| Python packaging PEP | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4277980 — 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 517 Context triple: [pip, implements, PEP 517]
-
A.
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.
-
B.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
C.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
D.
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.
-
E.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
- 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 517 Target entity description: PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
-
A.
PEP 508
PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
-
B.
PEP 503
PEP 503 is a Python Enhancement Proposal that defines the simple repository API used by package installers like pip to discover and download Python packages.
-
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 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
E.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| appliesTo | Python packaging ⓘ |
| author |
Donald Stufft
ⓘ
Nathaniel J. Smith ⓘ Thomas Kluyver ⓘ |
| created | 2015-09-29 ⓘ |
| defines |
build-system independent interface for building distributions
ⓘ
interface between front-end tools and build back-ends ⓘ |
| definesConcept |
build backend
ⓘ
build frontend ⓘ |
| definesHook |
build_editable
ⓘ
build_sdist ⓘ build_wheel ⓘ get_requires_for_build_editable ⓘ get_requires_for_build_sdist ⓘ get_requires_for_build_wheel ⓘ prepare_metadata_for_build_editable ⓘ prepare_metadata_for_build_wheel ⓘ |
| documentationURL | https://peps.python.org/pep-0517/ ⓘ |
| domain | software packaging standard ⓘ |
| enables |
isolation of build environments
ⓘ
use of non-setuptools build backends ⓘ |
| focusesOn |
building Python project distributions
ⓘ
source tree build configuration ⓘ |
| governingBody | Python Software Foundation ⓘ |
| governingProcess | Python PEP process ⓘ |
| language | Python ⓘ |
| motivation |
decouple build tools from setuptools
ⓘ
support multiple build systems consistently ⓘ |
| partOf | Python packaging standards ⓘ |
| relatedTo |
PEP 518
ⓘ
PEP 621 ⓘ Python packaging ecosystem ⓘ |
| requires | pyproject.toml build-system table (via PEP 518) ⓘ |
| specifiedIn | PEP 517 document ⓘ |
| standardizes |
build backend API
ⓘ
hooks for building source distributions ⓘ hooks for building wheels ⓘ metadata preparation hooks ⓘ |
| status | Final ⓘ |
| supersedesPractice | implicit setuptools-only builds ⓘ |
| targetCommunity |
Python package maintainers
ⓘ
Python packaging tool authors ⓘ |
| title | A build-system independent format for source trees ⓘ |
| type |
Standards Track PEP
ⓘ
linked to:
Standards Track
|
| usedBy |
build front-end tools
ⓘ
pip ⓘ |
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 517 Description of subject: PEP 517 is a Python packaging standard that defines a build-system independent interface for building Python project distributions.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
PEP 517 (via backends)
linked to: PEP 517
subject linked to:
PEP 517 (via backends)
linked to: PEP 517
subject linked to:
PEP 518 (pyproject.toml build-system)
subject linked to:
PEP 518 (pyproject.toml build-system)
subject linked to:
PEP 621 (project metadata in pyproject.toml, partially)