Movatterモバイル変換

Python Enhancement Proposals

Python »
PEP Index »
Release PEPs

Release PEPs

Introduction

This is the index of all Python Enhancement Proposals (PEPs) labelledunder 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 thedeveloper’s guide for more information.

Index by Category

Other Informational PEPs

	PEP	Title	Authors
IA	619	Python 3.10 Release Schedule	Pablo Galindo Salgado	3.10
IA	664	Python 3.11 Release Schedule	Pablo Galindo Salgado	3.11
IA	693	Python 3.12 Release Schedule	Thomas Wouters	3.12
IA	719	Python 3.13 Release Schedule	Thomas Wouters	3.13
IA	745	Python 3.14 Release Schedule	Hugo van Kemenade	3.14
IA	790	Python 3.15 Release Schedule	Hugo van Kemenade	3.15

Accepted PEPs (accepted; may not be implemented yet)

	PEP	Title	Authors
SA	773	A Python Installation Manager for Windows	Steve Dower

Historical Meta-PEPs and Informational PEPs

	PEP	Title	Authors
IF	160	Python 1.6 Release Schedule	Fred L. Drake, Jr.	1.6
IF	200	Python 2.0 Release Schedule	Jeremy Hylton	2.0
IF	226	Python 2.1 Release Schedule	Jeremy Hylton	2.1
IF	251	Python 2.2 Release Schedule	Barry Warsaw, Guido van Rossum	2.2
IF	283	Python 2.3 Release Schedule	Guido van Rossum	2.3
IF	320	Python 2.4 Release Schedule	Barry Warsaw, Raymond Hettinger, Anthony Baxter	2.4
IF	356	Python 2.5 Release Schedule	Neal Norwitz, Guido van Rossum, Anthony Baxter	2.5
IF	361	Python 2.6 and 3.0 Release Schedule	Neal Norwitz, Barry Warsaw	2.6, 3.0
IF	373	Python 2.7 Release Schedule	Benjamin Peterson	2.7
IF	375	Python 3.1 Release Schedule	Benjamin Peterson	3.1
IF	392	Python 3.2 Release Schedule	Georg Brandl	3.2
IF	398	Python 3.3 Release Schedule	Georg Brandl	3.3
IF	404	Python 2.8 Un-release Schedule	Barry Warsaw	2.8
IF	429	Python 3.4 Release Schedule	Larry Hastings	3.4
IF	478	Python 3.5 Release Schedule	Larry Hastings	3.5
IF	494	Python 3.6 Release Schedule	Ned Deily	3.6
IF	537	Python 3.7 Release Schedule	Ned Deily	3.7
IF	569	Python 3.8 Release Schedule	Łukasz Langa	3.8
IF	596	Python 3.9 Release Schedule	Łukasz Langa	3.9

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.

[8]ページ先頭

©2009-2025 Movatter.jp