PEPs
E51003
PEPs are formal design documents that propose and describe new features, processes, or changes for the Python programming language and its community.
Aliases (7)
- PEP ×71
- Informational PEP ×1
- Informational PEPs ×1
- Meta-PEPs ×1
- PEP 8016 ×1
- PEP index ×1
- PEP titles ×1
Statements (71)
| Predicate | Object |
|---|---|
| instanceOf |
Python community governance document
→
software development process document → |
| accessURL |
https://peps.python.org/
→
|
| coinedBy |
Barry Warsaw
→
|
| communityProcess |
discussion on Python Discourse
→
open discussion on python-dev mailing list → |
| decisionMaker |
Benevolent Dictator For Life (historical)
→
Python Steering Council → |
| documentedIn |
PEP 1 – PEP Purpose and Guidelines
→
|
| domain |
Python community
→
|
| editorRole |
to assign PEP numbers
→
to change PEP status according to decisions → to review PEPs for style and completeness → |
| format |
reStructuredText
→
|
| fullName |
Python Enhancement Proposal
→
|
| governedBy |
PEP 1
→
|
| governs |
Python development processes
→
Python language evolution → some aspects of Python community governance → |
| hasSection |
Abstract
→
Backwards Compatibility → Copyright → Motivation → Rationale → Reference Implementation → Specification → |
| hasType |
Informational PEP
→
Process PEP → Standards Track PEP → |
| hostedBy |
Python Software Foundation infrastructure
→
|
| hostedOn |
GitHub
→
|
| inspiredBy |
IETF RFC process
→
Java Community Process (JCP) → |
| introducedBy |
Barry Warsaw
→
|
| languageOfProject |
Python
→
|
| license |
Open publication license compatible with PSF policies
→
|
| maintainedBy |
PEP editors
→
Python Steering Council → Python core developers → |
| purpose |
to collect community input on an issue
→
to describe implementation details of Python features → to document design decisions for Python → to document the design rationale behind a feature → to propose new features for the Python programming language → to propose process changes for the Python community → to serve as a primary mechanism for proposing major new features → |
| relatedConcept |
Request for Comments (RFC)
→
language design proposal → |
| repository |
Python/peps Git repository
→
|
| reviewStage |
community review
→
steering council review → |
| scope |
Python governance structure
→
Python release process → interpreter behavior changes → language syntax changes → packaging standards → standard library additions or removals → |
| statusValue |
Accepted
→
Active → April Fools → Deferred → Draft → Final → Provisional → Rejected → Superseded → Withdrawn → |
| typicalAudience |
Python core developers
→
Python library authors → Python users interested in language evolution → |
| usedBy |
Python programming language
→
|
Referenced by (7)
| Subject (surface form when different) | Predicate |
|---|---|
|
PEP 0
("Meta-PEPs")
→
PEP 0 ("Informational PEPs") → |
hasSection |
|
Python Enhancement Proposals
→
|
abbreviation |
|
PEP 0
("PEP titles")
→
|
describes |
|
Process PEP
("PEP index")
→
|
documentedIn |
|
Python Enhancement Proposals
("PEP 8016")
→
|
hasPart |
|
PEP
("Informational PEP")
→
|
hasType |