PEP 621 (project metadata in pyproject.toml, partially)
E427620
PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 621 (project metadata in pyproject.toml, partially) canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4278081 — 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 621 (project metadata in pyproject.toml, partially) Context triple: [setuptools, supportsStandard, PEP 621 (project metadata in pyproject.toml, partially)]
-
A.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
B.
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.
-
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.
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.
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
- 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 621 (project metadata in pyproject.toml, partially) Target entity description: PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `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 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
D.
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.
-
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 ⓘ |
| aimsTo |
reduce metadata fragmentation in Python packaging
ⓘ
unify project metadata across build backends ⓘ |
| allows | build backends to read standardized metadata from pyproject.toml ⓘ |
| appliesTo | pyproject.toml ⓘ |
| category | Packaging ⓘ |
| compatibleWith |
PEP 517
ⓘ
PEP 518 ⓘ |
| createdFor | Python packaging ecosystem ⓘ |
| defines |
canonical location for core project metadata
ⓘ
rules for static versus dynamic metadata fields ⓘ standardized way to declare project metadata in pyproject.toml ⓘ |
| discourages | tool-specific duplication of core metadata ⓘ |
| encourages | tool-agnostic metadata definitions ⓘ |
| focusesOn | project metadata ⓘ |
| governs |
how project metadata is declared for distribution on Python Package Index (PyPI)
ⓘ
how tools like build backends interpret [project] metadata ⓘ metadata fields in pyproject.toml ⓘ |
| hostedOn |
python.org PEP index
ⓘ
linked to:
Python PEP index
|
| introduces | dynamic field list for metadata computed by build backends ⓘ |
| language | English ⓘ |
| maintainedBy | Python Packaging Authority ⓘ |
| partOf | Python packaging standards ⓘ |
| recommends | using the [project] table in pyproject.toml ⓘ |
| relatedTo |
Python packaging metadata standards
ⓘ
linked to:
Python packaging ecosystem
|
| replaces |
setup.cfg metadata for many use cases
ⓘ
setup.py metadata for many use cases ⓘ |
| scope | core project metadata, not build-system configuration ⓘ |
| separates | project metadata from build-system configuration ⓘ |
| standardizes |
project authors field
ⓘ
project classifiers field ⓘ project dependencies field ⓘ project description field ⓘ project entry-points via scripts tables ⓘ project license field ⓘ project maintainers field ⓘ project metadata keys in pyproject.toml ⓘ project name field ⓘ project optional-dependencies field ⓘ project readme field ⓘ project urls field ⓘ project version field ⓘ |
| status | Final ⓘ |
| title | Storing project metadata in pyproject.toml ⓘ |
| type | Standards Track ⓘ |
| usedBy |
build backends such as Hatchling, Flit, and others
ⓘ
modern Python packaging tools ⓘ |
| usesFileFormat | TOML ⓘ |
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 621 (project metadata in pyproject.toml, partially) Description of subject: PEP 621 is a Python packaging standard that defines a standardized way to declare project metadata in the `pyproject.toml` file.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.