python-peplisted

# python-pep Produces a **Python Enhancement Proposal**: the standardized design document the CPython community uses to propose and record changes. A PEP argues a change on its merits, specifies it precisely enough to implement, and survives review by the Steering Council or a delegate. It is *not* a tutorial, a changelog, or a bug report — it is a durable, reviewable design record. ## The three PEP types - **Standards Track** — a new feature or implementation change to Python (the language, the C API, or the standard library). Most PEPs are this type. - **Informational** — design guidance, conventions, or community information that does not propose a new feature (e.g. the release schedule). - **Process** — a change to a process *around* Python (decision-making, governance, tooling) rather than the language itself. ## Status lifecycle ```text Draft ──> Accepted ──> Final │ │ ├─> Rejected (turned down on its merits) ├─> Withdrawn (the author abandons it) ├─> Deferred (no champion / not ready) └─> Superseded (replaced by a later PEP) ``` - A PEP opens as **Draft**. Standards Track PEPs may pass through **Provisional/Accepted** before reaching **Final** once the reference implementation lands. - **Rejected**, **Withdrawn**, and **Deferred** are terminal-for-now outcomes; **Superseded** points forward to the PEP that replaced it. - **The header's `Status:` field always reflects exactly one of these states at a t