python/peps

Python Enhancement Proposals

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 seconds ago
Added to GitGenius on September 13th, 2026
Created on October 8th, 2013
Open Issues & Pull Requests: 65 (+0)
GitHub issues: Enabled
Number of forks: 1,807
Total Stargazers: 5,007 (+0)
Total Subscribers: 275 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 37.8 days
90th percentile: 8.9 days
Tracked items: 87

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 563 days
Stale 30+ days: 9
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 3

Top labels

  • invalid (14)
  • infra (9)
  • meta (7)
  • bug (2)
  • question (2)
  • enhancement (1)

Most active issues this week

Detailed Description

PEPs is a repository that hosts Python Enhancement Proposals, the formal documents that guide Python language evolution and standardization.

The repository solves the problem of centrally managing, organizing, and publishing the proposals that shape Python's development. PEPs are structured documents written in reStructuredText that describe new features, processes, or standards for the Python community. The repository automatically renders these proposals to a public website, generates an index based on metadata headers in each proposal, and provides both canonical zero-padded links and shortcut redirects for easy access. An API also exposes PEP data in structured formats.

Anyone contributing to or reading PEPs should know that the repository enforces reStructuredText syntax validation to prevent rendering failures. Contributors can preview their changes through automatic Read the Docs builds on pull requests before merging. Local rendering is supported through a build system that requires installing dependencies and running either a make command or a Python build script. The repository includes linting and spelling checks via a pre-commit suite to catch common issues early. This is the canonical source for Python Enhancement Proposals; there are no alternatives mentioned.

The project maintains automated rendering workflows that validate syntax and generate the published website on every change. Contribution guidelines and build documentation are actively maintained alongside the proposal content itself. The repository uses pre-commit tooling to enforce quality standards before code is committed.