Showing content from https://peps.python.org/pep-0719/../topic/release/ below:
Release PEPs | peps.python.org
Python Enhancement Proposals Release PEPs Introduction
This is the index of all Python Enhancement Proposals (PEPs) labelled under the ‘Release’ topic. This is a sub-index of PEP 0, the PEP index.
A PEP is written to specify the release cycle for each feature release of Python. See the developer’s guide for more information.
Index by Category Other Informational PEPs Accepted PEPs (accepted; may not be implemented yet) Historical Meta-PEPs and Informational PEPs PEP Types Key
- I — Informational: Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem
- P — Process: Normative PEP describing or proposing a change to a Python community process, workflow or governance
- S — Standards Track: Normative PEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem
More info in PEP 1.
PEP Status Key
- A — Accepted: Normative proposal accepted for implementation
- A — Active: Currently valid informational guidance, or an in-use process
- D — Deferred: Inactive draft that may be taken up again at a later time
- <No letter> — Draft: Proposal under active discussion and revision
- F — Final: Accepted and implementation complete, or no longer active
- P — Provisional: Provisionally accepted but additional feedback needed
- R — Rejected: Formally declined and will not be accepted
- S — Superseded: Replaced by another succeeding PEP
- W — Withdrawn: Removed from consideration by sponsor or authors
More info in PEP 1.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4