PEP 508
E426702
PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
All labels observed (3)
| Label | Occurrences |
|---|---|
| PEP 508 canonical | 6 |
| Dependency specification for Python Software Packages | 1 |
| PEP 508 – Dependency specification for Python Software Packages | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4277979 — 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 508 Context triple: [pip, implements, PEP 508]
-
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 635
PEP 635 is a Python Enhancement Proposal that provides a detailed rationale and motivation for the structural pattern matching feature 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 508 Target entity description: PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
-
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 635
PEP 635 is a Python Enhancement Proposal that provides a detailed rationale and motivation for the structural pattern matching feature introduced in Python 3.10.
- F. None of above. chosen
Statements (52)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| appliesTo |
Python package metadata
ⓘ
Python packaging tools ⓘ pip ⓘ setuptools ⓘ |
| author |
Donald Stufft
ⓘ
Marcus Smith ⓘ Nick Coghlan ⓘ |
| created | 2015-09-07 ⓘ |
| defines |
standard syntax for direct URL references
ⓘ
standard syntax for environment markers ⓘ standard syntax for extras ⓘ standard syntax for specifying package dependencies ⓘ standard syntax for version specifiers ⓘ |
| definesConcept |
direct reference
ⓘ
environment marker ⓘ extra ⓘ normalized requirement string ⓘ version specifier ⓘ |
| directReferenceExample | package @ https://example.com/package-1.0.tar.gz ⓘ |
| discussionsTo | distutils-sig@python.org ⓘ |
| documentationURL | https://peps.python.org/pep-0508/ ⓘ |
| environmentMarkerExample |
extra == "security"
ⓘ
python_version == "3.8" ⓘ sys_platform == "win32" ⓘ |
| extraExample | requests[security] ⓘ |
| field | Python packaging ⓘ |
| governs |
syntax of direct URL references in requirement strings
ⓘ
syntax of environment markers in requirement strings ⓘ syntax of extras in requirement strings ⓘ syntax of requirement strings ⓘ |
| hostProject | Python ⓘ |
| influences |
Python packaging interoperability standards
ⓘ
pip dependency resolution behavior ⓘ |
| language | Python ⓘ |
| maintainedBy | Python Packaging Authority ⓘ |
| markerSyntaxBasedOn | PEP 345 ⓘ |
| partOf |
Python packaging specifications ecosystem
ⓘ
linked to:
Python packaging ecosystem
|
| relatedTo |
PEP 440
ⓘ
PEP 517 ⓘ PEP 518 ⓘ |
| replaces | PEP 426 ⓘ |
| shortTitle |
Dependency specification for Python Software Packages
ⓘ
linked to:
PEP 508
|
| status | Final ⓘ |
| supersedes | earlier informal dependency specification conventions ⓘ |
| title |
PEP 508 – Dependency specification for Python Software Packages
ⓘ
linked to:
PEP 508
|
| type | Standards Track ⓘ |
| usedIn |
install_requires in setup.py
ⓘ
metadata fields like Requires-Dist ⓘ pyproject.toml dependency tables ⓘ requirements.txt files ⓘ |
| versionSpecifierExample | >=1.0,<2.0 ⓘ |
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 508 Description of subject: PEP 508 is a Python Enhancement Proposal that defines the standard syntax for specifying package dependencies and environment markers in Python packaging.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.