wtf is peps?

This repository holds Python Enhancement Proposals, formal documents that describe new features, improvements, or changes to the Python programming language itself. Think of PEPs as the official suggestion box and decision log for Python's development. When someone wants to propose a major change to how Python works, they write a PEP, the community discusses it, and if approved, it becomes part of the language's roadmap. The repo contains hundreds of these proposals in a structured text format. They're automatically published and made viewable on the web at peps.python.org, so anyone can read the current state of Python's evolution. Each PEP gets a number (like PEP 8, which defines Python's style guidelines), and the repository keeps them all organized, versioned, and searchable. There's also an automatically-generated index that makes it easy to browse what's been proposed and decided. If you're involved in Python's development, whether as a core contributor, library maintainer, or someone who wants to influence the language's direction, this is where you'd come to propose ideas or weigh in on others' proposals. You can submit a PEP by contributing to this repository, and the system will automatically preview how it will look on the website before it's published. For maintainers, the repository includes tools to check that proposals are properly formatted and don't have errors before they go live. The README emphasizes that contributors should make sure their submissions render correctly before committing, and points to guides for both writing new PEPs and checking your work locally or through automated previews. It's a straightforward document management system designed specifically for the formal, collaborative process of evolving Python itself.