Disambiguation evidence for PEPs via surface form
"PEP"
As subject (71)
Triples where this entity appears as subject under the
label "PEP".
| Predicate | Object |
|---|---|
| accessURL | https://peps.python.org/ ⓘ |
| coinedBy | Barry Warsaw ⓘ |
| communityProcess | discussion on Python Discourse ⓘ |
| communityProcess | open discussion on python-dev mailing list ⓘ |
| decisionMaker | Benevolent Dictator For Life (historical) ⓘ |
| decisionMaker | Python Steering Council ⓘ |
| documentedIn | PEP 1 – PEP Purpose and Guidelines ⓘ |
| domain | Python community ⓘ |
| editorRole | to assign PEP numbers ⓘ |
| editorRole | to change PEP status according to decisions ⓘ |
| editorRole | 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 ⓘ |
| governs | Python language evolution ⓘ |
| governs | some aspects of Python community governance ⓘ |
| hasSection | Abstract ⓘ |
| hasSection | Backwards Compatibility ⓘ |
| hasSection | Copyright ⓘ |
| hasSection | Motivation ⓘ |
| hasSection | Rationale ⓘ |
| hasSection | Reference Implementation ⓘ |
| hasSection | Specification ⓘ |
| hasType |
PEPs
self-linksurface differs
ⓘ
surface form:
Informational PEP
|
| hasType | Process PEP ⓘ |
| hasType |
Standards Track
ⓘ
surface form:
Standards Track PEP
|
| hostedBy | Python Software Foundation infrastructure ⓘ |
| hostedOn | GitHub ⓘ |
| inspiredBy | IETF RFC process ⓘ |
| inspiredBy |
Java Community Process
ⓘ
surface form:
Java Community Process (JCP)
|
| instanceOf | Python community governance document ⓘ |
| instanceOf | software development process document ⓘ |
| introducedBy | Barry Warsaw ⓘ |
| languageOfProject | Python ⓘ |
| license | Open publication license compatible with PSF policies ⓘ |
| maintainedBy | PEP editors ⓘ |
| maintainedBy | Python Steering Council ⓘ |
| maintainedBy | Python core developers ⓘ |
| purpose | to collect community input on an issue ⓘ |
| purpose | to describe implementation details of Python features ⓘ |
| purpose | to document design decisions for Python ⓘ |
| purpose | to document the design rationale behind a feature ⓘ |
| purpose | to propose new features for the Python programming language ⓘ |
| purpose | to propose process changes for the Python community ⓘ |
| purpose | to serve as a primary mechanism for proposing major new features ⓘ |
| relatedConcept |
RFCs
ⓘ
surface form:
Request for Comments (RFC)
|
| relatedConcept | language design proposal ⓘ |
| repository | Python/peps Git repository ⓘ |
| reviewStage | community review ⓘ |
| reviewStage | steering council review ⓘ |
| scope | Python governance structure ⓘ |
| scope | Python release process ⓘ |
| scope | interpreter behavior changes ⓘ |
| scope | language syntax changes ⓘ |
| scope | packaging standards ⓘ |
| scope | standard library additions or removals ⓘ |
| statusValue | Accepted ⓘ |
| statusValue | Active ⓘ |
| statusValue | April Fools ⓘ |
| statusValue | Deferred ⓘ |
| statusValue | Draft ⓘ |
| statusValue | Final ⓘ |
| statusValue | Provisional ⓘ |
| statusValue | Rejected ⓘ |
| statusValue | Superseded ⓘ |
| statusValue | Withdrawn ⓘ |
| typicalAudience | Python core developers ⓘ |
| typicalAudience | Python library authors ⓘ |
| typicalAudience | Python users interested in language evolution ⓘ |
| usedBy |
Python
ⓘ
surface form:
Python programming language
|