PEP 440
E427615
PEP 440 is the Python Packaging Authority’s standard that defines a consistent versioning scheme for Python packages.
All labels observed (2)
| Label | Occurrences |
|---|---|
| PEP 440 canonical | 2 |
| PEP 440 (versioning scheme) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4277982 — 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 440 Context triple: [pip, implements, PEP 440]
-
A.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
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 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 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.
-
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
- 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 440 Target entity description: PEP 440 is the Python Packaging Authority’s standard that defines a consistent versioning scheme for Python packages.
-
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.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
E.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
Python Enhancement Proposal
ⓘ
software versioning specification ⓘ |
| appliesTo |
Python package distributions
ⓘ
Python packaging ecosystem ⓘ |
| author | Donald Stufft NERFINISHED ⓘ |
| created | 2013-08-09 ⓘ |
| defines |
dependency version specifiers for Python packages
ⓘ
normalized version representation for Python packages ⓘ standard version scheme for Python packages ⓘ |
| definesBehavior |
how development releases compare to other releases
ⓘ
how local versions affect version ordering ⓘ how post-releases compare to corresponding releases ⓘ how pre-releases compare to final releases ⓘ ordering of version identifiers ⓘ |
| definesConcept |
development release segment in version numbers
ⓘ
developmental releases ⓘ epoch segment in version numbers ⓘ local version identifiers ⓘ local version segment in version numbers ⓘ post-release segment in version numbers ⓘ post-release versions ⓘ pre-release segment in version numbers ⓘ pre-release versions ⓘ public version identifiers ⓘ release segment in version numbers ⓘ |
| definesFormat |
canonical local version format
ⓘ
canonical public version format ⓘ normalization rules for version comparison ⓘ |
| documentationURL | https://peps.python.org/pep-0440/ ⓘ |
| governingBody |
Python Packaging Authority
NERFINISHED
ⓘ
Python Software Foundation NERFINISHED ⓘ |
| language | English ⓘ |
| partOf | Python packaging specifications ⓘ |
| relatedTo |
PEP 425
NERFINISHED
ⓘ
PEP 427 NERFINISHED ⓘ PEP 508 NERFINISHED ⓘ |
| replaces | PEP 386 NERFINISHED ⓘ |
| scope | Python packaging and distribution tools ⓘ |
| specifiesSyntax |
PEP 440 compliant version string
ⓘ
compatible release operator ~= ⓘ environment marker version constraints ⓘ version specifiers like ==, !=, <=, >=, ~=, ===, <, > ⓘ wildcard version matching with * ⓘ |
| status | Active ⓘ |
| supersedes | legacy Python package versioning practices ⓘ |
| title | PEP 440 – Version Identification and Dependency Specification NERFINISHED ⓘ |
| type | Standards Track ⓘ |
| usedBy |
build backends compliant with Python packaging standards
ⓘ
pip NERFINISHED ⓘ setuptools NERFINISHED ⓘ wheel ⓘ |
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 440 Description of subject: PEP 440 is the Python Packaging Authority’s standard that defines a consistent versioning scheme for Python packages.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
PEP 440 (versioning scheme)