NewsPEPper
Python changes, weekly and brief.
NewsPEPper tracks new Python Enhancement Proposals and every status change, then writes a short note on what each one means for your code. New to PEPs? Start with the basics.
Or follow the RSS feed.
Issues
No issues yet. The first one goes out on the next weekly run.
About PEPs
Python Enhancement Proposals (PEPs) are how changes to Python are proposed and decided. PEP 1 explains the process.
Statuses
- Accepted
- Normative proposal accepted for implementation
- Active
- Currently valid informational guidance, or an in-use process
- Deferred
- Inactive draft that may be taken up again at a later time
- Draft
- Proposal under active discussion and revision
- Final
- Accepted and implementation complete, or no longer active
- Provisional
- Provisionally accepted but additional feedback needed
- Rejected
- Formally declined and will not be accepted
- Superseded
- Replaced by another succeeding PEP
- Withdrawn
- Removed from consideration by sponsor or authors
Types
- Informational
- Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem
- Process
- Normative PEP describing or proposing a change to a Python community process, workflow or governance
- Standards Track
- Normative PEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem
Reading an issue
Draft→Accepted- The status. When it changed since the last issue, the old one is struck through.
- 3.15
- The Python version the PEP targets.
- Typing
- Its topic, if it has one.
- Decision
- A link to the post that accepted or rejected it, or to the discussion until there is one.
In a week with a new Python release, or a Python version that changes support (such as reaching end of life), the issue ends with a Python releases section.
Statuses and types as the PEP index defines them.