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 Disambiguation Statements Elicitation Referenced by

All labels observed (11)

Label	Occurrences
Informational PEP	2
Informational PEPs	2
Deferred PEPs	1
Implementation PEP	1
Library PEP	1
Meta-PEPs	1
PEP 8016	1
PEP editors	1
PEP index	1
PEP titles	1
PEPs canonical	1

How this entity was disambiguated

This entity first appeared as the object of triple T400399 — 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.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: PEPs
Context triple: [Python Enhancement Proposals, abbreviation, PEPs]

A. Pep
Pep is the widely used nickname of Josep "Pep" Guardiola, the renowned Spanish football manager and former player.
B. PE
PE is the two-letter ISO 3166-1 alpha-2 country code assigned to Peru for international standardization and referencing.
C. BEP
BEP is a United States government agency responsible for designing and producing paper currency and other secure documents.
D. EOP
EOP is the collective group of offices and agencies that directly support the President of the United States in carrying out executive responsibilities and policy initiatives.
E. PEG
PEG is the stock ticker symbol for Public Service Enterprise Group, a major U.S. energy company primarily involved in regulated electric and gas utility operations and power generation.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

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

A. Pep
Pep is the widely used nickname of Josep "Pep" Guardiola, the renowned Spanish football manager and former player.
B. PE
PE is the two-letter ISO 3166-1 alpha-2 country code assigned to Peru for international standardization and referencing.
C. BEP
BEP is a United States government agency responsible for designing and producing paper currency and other secure documents.
D. EOP
EOP is the collective group of offices and agencies that directly support the President of the United States in carrying out executive responsibilities and policy initiatives.
E. PEG
PEG is the stock ticker symbol for Public Service Enterprise Group, a major U.S. energy company primarily involved in regulated electric and gas utility operations and power generation.
F. None of above. chosen

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

How these facts were elicited

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 ⓘ