PEP 425 platform compatibility tags
E426699
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 425 platform compatibility tags canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4277939 — 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.
Target entity: PEP 425 platform compatibility tags Context triple: [Python Packaging Authority, develops, PEP 425 platform compatibility tags]
-
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 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
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.
Target entity: PEP 425 platform compatibility tags Target entity description: 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.
-
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 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
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
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Python packaging standard
ⓘ
compatibility tag scheme ⓘ |
| abiTagExample |
abi3
ⓘ
cp39 ⓘ none ⓘ |
| appliesTo |
Python wheels
NERFINISHED
ⓘ
built Python distributions ⓘ |
| backwardsCompatibleWith | older Python packaging tools that understand tags ⓘ |
| definedIn | PEP 425 NERFINISHED ⓘ |
| distinguishes | platform-specific wheels from pure-Python wheels ⓘ |
| enables |
filtering incompatible binary distributions
ⓘ
selection of appropriate wheel for target environment ⓘ |
| example |
cp310-cp310-win_amd64
ⓘ
cp311-abi3-macosx_11_0_arm64 ⓘ cp39-cp39-manylinux2014_x86_64 ⓘ py3-none-any ⓘ |
| format | interpreter-abi-platform ⓘ |
| hasComponent |
ABI tag
ⓘ
interpreter tag ⓘ platform tag ⓘ |
| interpreterTagExample |
cp310
ⓘ
cp39 ⓘ py3 ⓘ |
| introducedConcept | standardized wheel compatibility tags ⓘ |
| partOf | Python Enhancement Proposal 425 NERFINISHED ⓘ |
| platformTagExample |
any
ⓘ
macosx_11_0_arm64 ⓘ manylinux2014_x86_64 ⓘ win_amd64 ⓘ |
| purePythonTag | py3-none-any ⓘ |
| relatedTo |
PEP 427
NERFINISHED
ⓘ
Python wheel format ⓘ |
| scope | CPython and other Python interpreters ⓘ |
| standardizedBy | Python Packaging Authority NERFINISHED ⓘ |
| status | accepted Python Enhancement Proposal specification ⓘ |
| supports | multiple tags per distribution ⓘ |
| usedBy |
Python package indexes such as PyPI
ⓘ
build backends for Python packaging ⓘ pip NERFINISHED ⓘ setuptools ⓘ wheel ⓘ |
| usedFor |
indicating supported ABI (Application Binary Interface)
ⓘ
indicating supported CPU architectures ⓘ indicating supported Python versions ⓘ indicating supported operating systems ⓘ specifying compatibility of built Python distributions ⓘ |
| usedIn |
Python binary distribution metadata
ⓘ
Python wheel filenames ⓘ |
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.
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.
Subject: PEP 425 platform compatibility tags Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.