PEPs

E51003
Python community governance document software development process document

PEPs are formal design documents that propose and describe new features, processes, or changes for the Python programming language and its community.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (11)

Label Occurrences
Informational PEP 2
Informational PEPs 2
Deferred PEPs 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 Proposals ⓘ
surface form: 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 PEPs self-linksurface differs ⓘ
surface form: Informational PEP

Process PEP ⓘ
Standards Track ⓘ
surface form: Standards Track PEP
hostedBy Python Software Foundation infrastructure ⓘ
hostedOn GitHub ⓘ
inspiredBy IETF RFC process ⓘ
Java Community Process ⓘ
surface form: 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 RFCs ⓘ
surface form: 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 ⓘ
surface form: Python programming language

Referenced by (13)

Full triples — surface form annotated when it differs from this entity's canonical label.

Python Enhancement Proposals → abbreviation → PEPs ⓘ
Python Enhancement Proposals → hasPart → PEPs ⓘ
this entity surface form: PEP 8016
PEPs → hasType → PEPs self-linksurface differs ⓘ
subject surface form: PEP
this entity surface form: Informational PEP
PEP 0 → hasSection → PEPs ⓘ
this entity surface form: Meta-PEPs
PEP 0 → hasSection → PEPs ⓘ
this entity surface form: Informational PEPs
PEP 0 → describes → PEPs ⓘ
this entity surface form: PEP titles
Process PEP → documentedIn → PEPs ⓘ
this entity surface form: PEP index
Standards Track → hasSubcategory → PEPs ⓘ
this entity surface form: Library PEP
Standards Track → hasSubcategory → PEPs ⓘ
this entity surface form: Implementation PEP
Standards Track → contrastedWith → PEPs ⓘ
this entity surface form: Informational PEP
PEP 1 – PEP Purpose and Guidelines → defines → PEPs ⓘ
this entity surface form: PEP editors
Provisional PEPs → relatedTo → PEPs ⓘ
this entity surface form: Deferred PEPs
Standards Track PEPs → distinguishedFrom → PEPs ⓘ
this entity surface form: Informational PEPs