PEP 517 (via backends)
E427617
PEP 517 (via backends) defines a standardized, backend-agnostic interface for building Python packages, separating build logic from packaging tools like setuptools.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 517 (via backends) canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4278077 — 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 (via backends) Context triple: [setuptools, supportsStandard, PEP 517 (via backends)]
-
A.
Python Packaging Authority
The Python Packaging Authority is a working group that oversees and develops key tools, standards, and infrastructure for packaging and distributing Python software.
-
B.
setuptools
setuptools is a widely used Python library for packaging, distributing, and installing Python projects and their dependencies.
-
C.
Pipenv
Pipenv is a Python packaging and dependency management tool that combines virtual environment handling with a Pipfile-based workflow to simplify and standardize project setup.
-
D.
pip
pip is the standard command-line package manager for Python, used to install and manage software packages from the Python Package Index (PyPI) and other repositories.
-
E.
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.
- 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 (via backends) Target entity description: PEP 517 (via backends) defines a standardized, backend-agnostic interface for building Python packages, separating build logic from packaging tools like setuptools.
-
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 425 platform compatibility tags
PEP 425 platform compatibility tags are standardized identifiers used in Python packaging to specify which operating systems, architectures, and Python versions a built distribution (like a wheel) is compatible with.
-
D.
Python Packaging Authority
The Python Packaging Authority is a working group that oversees and develops key tools, standards, and infrastructure for packaging and distributing Python software.
-
E.
setuptools
setuptools is a widely used Python library for packaging, distributing, and installing Python projects and their dependencies.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| affects | how Python source trees are built into distributions ⓘ |
| aimsTo |
decouple build tools from specific packaging implementations
ⓘ
improve interoperability between Python packaging tools ⓘ |
| allows | projects to choose arbitrary build backends ⓘ |
| appliesTo | Python packaging ecosystem ⓘ |
| category |
Python packaging PEP
ⓘ
linked to:
PEP 517
|
| clarifies | responsibilities of build frontends versus build backends ⓘ |
| defines |
backend-agnostic interface for building Python packages
ⓘ
contract between build frontends and build backends ⓘ error handling and reporting expectations for build backends ⓘ standard interface between Python packaging frontends and build backends ⓘ |
| describes | build-system independent format for Python source trees ⓘ |
| doesNotRequire | use of setuptools as the build backend ⓘ |
| domain | software packaging ⓘ |
| enables |
backend-agnostic tooling for building Python distributions
ⓘ
use of alternative build backends such as flit ⓘ use of alternative build backends such as hatchling ⓘ use of alternative build backends such as poetry-core ⓘ use of alternative build backends such as setuptools.build_meta ⓘ |
| introduces |
concept of build backends
ⓘ
concept of build frontends ⓘ |
| isDocumentedAt | https://peps.python.org/pep-0517/ ⓘ |
| isImplementedIn |
Python packaging tools ecosystem
ⓘ
modern versions of pip ⓘ |
| isPartOf | Python packaging specifications ⓘ |
| isReferencedBy |
Python packaging documentation
ⓘ
third-party build backends documentation ⓘ |
| isRelatedTo | PEP 518 ⓘ |
| isUsedBy |
build frontends such as pip, build, and others
ⓘ
pip as a build frontend ⓘ |
| language | Python ⓘ |
| replaces | implicit setuptools-only build model ⓘ |
| requires | build backends to expose specific hook functions ⓘ |
| scope | build-time behavior of Python projects ⓘ |
| separates |
build logic from packaging frontends
ⓘ
build logic from tools like setuptools ⓘ |
| specifies |
hooks for building source distributions
ⓘ
hooks for building wheels ⓘ hooks for preparing metadata ⓘ |
| standardizes | how frontends invoke build backends ⓘ |
| status | Accepted ⓘ |
| supports | multiple build backends for Python projects ⓘ |
| title |
PEP 517 – A build-system independent format for source trees
ⓘ
linked to:
PEP 517
|
| uses | pyproject.toml for build-system configuration (via PEP 518) ⓘ |
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 (via backends) Description of subject: PEP 517 (via backends) defines a standardized, backend-agnostic interface for building Python packages, separating build logic from packaging tools like setuptools.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.