PEP 503
E426701
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 503 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4277978 — 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 503 Context triple: [pip, implements, PEP 503]
-
A.
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.
-
B.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced 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.
Target entity: PEP 503 Target entity description: 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.
-
A.
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.
-
B.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced 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
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| appliesTo | Python package indexes ⓘ |
| audience |
Python package index maintainers
ⓘ
Python packaging ecosystem developers ⓘ Python packaging tool authors ⓘ |
| createdBy |
Alex Grönholm
NERFINISHED
ⓘ
Barry Warsaw NERFINISHED ⓘ Brett Cannon NERFINISHED ⓘ Daniel Holth NERFINISHED ⓘ Donald Stufft NERFINISHED ⓘ Ernest W. Durbin III NERFINISHED ⓘ Holger Krekel NERFINISHED ⓘ Hynek Schlawack NERFINISHED ⓘ Maciej Szulik NERFINISHED ⓘ Marc-Andre Lemburg NERFINISHED ⓘ Nathaniel J. Smith NERFINISHED ⓘ Nick Coghlan NERFINISHED ⓘ Paul Moore NERFINISHED ⓘ Richard Jones NERFINISHED ⓘ |
| defines |
"/simple/" endpoint for package index servers
ⓘ
backwards-compatible subset of the legacy PyPI simple API ⓘ how installers discover available distributions for a project ⓘ link format for distribution files in simple indexes ⓘ rules for normalizing Python project names in URLs ⓘ simple repository API for Python package indexes ⓘ use of rel="nofollow" and other link attributes in simple indexes ⓘ |
| discussedOn | Distutils-SIG mailing list NERFINISHED ⓘ |
| governs |
HTML structure of simple index pages
ⓘ
caching and mirroring behavior for simple indexes ⓘ layout of simple repository index pages ⓘ normalized project name URLs in simple indexes ⓘ use of HTTPS for simple repository API ⓘ |
| hostedAt | https://peps.python.org/pep-0503/ ⓘ |
| language | English ⓘ |
| motivation |
enable interoperability between different Python package indexes and installers
ⓘ
provide a stable, well-defined API for Python package indexes ⓘ |
| programmingLanguage | Python ⓘ |
| relatedTo |
PEP 425
NERFINISHED
ⓘ
PEP 427 NERFINISHED ⓘ PEP 440 NERFINISHED ⓘ PyPI NERFINISHED ⓘ |
| replaces | informal legacy simple API documentation for PyPI ⓘ |
| repositoryAPIName | simple ⓘ |
| specifies | API used by Python package installers to discover and download packages ⓘ |
| standardizedFor | Python packaging ecosystem ⓘ |
| status | Final ⓘ |
| title | Simple Repository API NERFINISHED ⓘ |
| type | Standards Track PEP ⓘ |
| usedBy |
Python package installers
ⓘ
pip NERFINISHED ⓘ |
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 503 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.