PEP 518 (pyproject.toml build-system)

E427618

Python Enhancement Proposal

PEP 518 (pyproject.toml build-system) is a Python packaging standard that defines how projects declare their build requirements and configuration in a pyproject.toml file.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (2)

Label	Occurrences
PEP 518	2
PEP 518 (pyproject.toml build-system) canonical	1

How this entity was disambiguated

This entity first appeared as the object of triple T4278078 — 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 (pyproject.toml build-system)
Context triple: [setuptools, supportsStandard, PEP 518 (pyproject.toml build-system)]

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 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.
D. PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
E. 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.
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 (pyproject.toml build-system)
Target entity description: PEP 518 (pyproject.toml build-system) is a Python packaging standard that defines how projects declare their build requirements and configuration in a pyproject.toml file.

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 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.
F. None of above. chosen

Statements (48)

Predicate	Object
instanceOf	Python Enhancement Proposal ⓘ
affects	source distribution build process ⓘ wheel build process ⓘ
appliesTo	Python packaging ⓘ
assumes	TOML parser availability ⓘ
author	Donald Stufft NERFINISHED ⓘ Nathaniel J. Smith NERFINISHED ⓘ Thomas Kluyver NERFINISHED ⓘ
category	Python packaging standard ⓘ
clarifies	responsibilities of frontends and backends in builds ⓘ
context	Python packaging interoperability ⓘ
defines	[build-system] table in pyproject.toml ⓘ pyproject.toml build-system table ⓘ
definesField	build-system.backend-path ⓘ build-system.build-backend ⓘ build-system.requires ⓘ
definesKey	[build-system] in pyproject.toml ⓘ
definesLocation	build configuration in pyproject.toml instead of setup.cfg ⓘ
discusses	build-time dependencies ⓘ isolation of build environments ⓘ minimum build system requirements ⓘ
enables	backend-agnostic builds ⓘ declarative build requirements ⓘ
fileName	pyproject.toml ⓘ
goal	enable build isolation ⓘ separate build configuration from setup.py ⓘ standardize declaration of build requirements ⓘ
governs	minimum requirements for building a project ⓘ
influenced	adoption of pyproject.toml across Python projects ⓘ
introducedConcept	pyproject.toml file for build configuration ⓘ
introducedIn	Python packaging ecosystem ⓘ
language	Python NERFINISHED ⓘ
motivates	PEP 517 NERFINISHED ⓘ
primaryFileFormat	TOML NERFINISHED ⓘ
recommends	using isolated build environments ⓘ
relatedTo	PEP 517 NERFINISHED ⓘ PEP 621 NERFINISHED ⓘ PEP 660 NERFINISHED ⓘ
repository	https://peps.python.org/pep-0518/ ⓘ
scope	binary distributions ⓘ source distributions ⓘ
standardizes	how projects declare build dependencies ⓘ how tools discover build backends ⓘ
status	Final ⓘ
title	Specifying Minimum Build System Requirements for Python Projects NERFINISHED ⓘ
usedBy	Python packaging tools ⓘ build backends ⓘ pip NERFINISHED ⓘ

How these facts were elicited

Referenced by (3)

Full triples — surface form annotated when it differs from this entity's canonical label.

pip → implements → PEP 518 (pyproject.toml build-system) ⓘ

this entity surface form: PEP 518

setuptools → supportsStandard → PEP 518 (pyproject.toml build-system) ⓘ

Pipenv → followsStandard → PEP 518 (pyproject.toml build-system) ⓘ