-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Expand file tree
/
Copy pathindex.rst
More file actions
215 lines (188 loc) · 5.67 KB
/
Copy pathindex.rst
File metadata and controls
215 lines (188 loc) · 5.67 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
PEPs API
========
peps.json
---------
There is a read-only JSON document of every published PEP available at
https://peps.python.org/api/peps.json.
Each PEP is represented as a JSON object, keyed by the PEP number.
The structure of each JSON object is as follows:
.. code-block:: typescript
{
"<PEP number>": {
"number": integer, // always identical to <PEP number>
"title": string,
"authors": string,
"discussions_to": string | null,
"status": "Accepted" | "Active" | "Deferred" | "Draft" | "Final" | "Provisional" | "Rejected" | "Superseded" | "Withdrawn",
"type": "Informational" | "Process" | "Standards Track",
"topic": "governance" | "packaging" | "release" | "typing" | "",
"created": string,
"python_version": string | null,
"post_history": string | null,
"resolution": string | null,
"requires": string | null,
"replaces": string | null,
"superseded_by": string | null,
"author_names": Array<string>,
"url": string
},
}
Date values are formatted as DD-MMM-YYYY,
and multiple dates are combined in a comma-separated list.
A selection of example PEPs are shown here,
illustrating some of the possible values for each field:
.. code-block:: json
{
"12": {
"number": 12,
"title": "Sample reStructuredText PEP Template",
"authors": "David Goodger, Barry Warsaw, Brett Cannon",
"discussions_to": null,
"status": "Active",
"type": "Process",
"topic": "",
"created": "05-Aug-2002",
"python_version": null,
"post_history": "`30-Aug-2002 <https://mail.python.org/archives/list/python-dev@python.org/thread/KX3AS7QAY26QH3WIUAEOCCNXQ4V2TGGV/>`__",
"resolution": null,
"requires": null,
"replaces": null,
"superseded_by": null,
"author_names": [
"David Goodger",
"Barry Warsaw",
"Brett Cannon"
],
"url": "https://peps.python.org/pep-0012/"
},
"160": {
"number": 160,
"title": "Python 1.6 Release Schedule",
"authors": "Fred L. Drake, Jr.",
"discussions_to": null,
"status": "Final",
"type": "Informational",
"topic": "release",
"created": "25-Jul-2000",
"python_version": "1.6",
"post_history": null,
"resolution": null,
"requires": null,
"replaces": null,
"superseded_by": null,
"author_names": [
"Fred L. Drake, Jr."
],
"url": "https://peps.python.org/pep-0160/"
},
"3124": {
"number": 3124,
"title": "Overloading, Generic Functions, Interfaces, and Adaptation",
"authors": "Phillip J. Eby",
"discussions_to": "python-3000@python.org",
"status": "Deferred",
"type": "Standards Track",
"topic": "",
"created": "28-Apr-2007",
"python_version": null,
"post_history": "30-Apr-2007",
"resolution": null,
"requires": "3107, 3115, 3119",
"replaces": "245, 246",
"superseded_by": null,
"author_names": [
"Phillip J. Eby"
],
"url": "https://peps.python.org/pep-3124/"
}
}
release-cycle.json
------------------
There is a read-only JSON document of Python releases
available at https://peps.python.org/api/release-cycle.json.
Each feature version is represented as a JSON object,
keyed by the minor version number ("X.Y").
The structure of each JSON object is as follows:
.. code-block:: typescript
{
"<language version number>": {
"branch": string,
"pep": integer,
"status": 'feature' | 'prerelease' | 'bugfix' | 'security' | 'end-of-life',
"first_release": string, // Date formatted as YYYY-MM-DD
"end_of_life": string, // Date formatted as YYYY-MM-DD
"release_manager": string
},
}
For example:
.. code-block:: json
{
"3.15": {
"branch": "main",
"pep": 790,
"status": "feature",
"first_release": "2026-10-01",
"end_of_life": "2031-10",
"release_manager": "Hugo van Kemenade"
},
"3.14": {
"branch": "3.14",
"pep": 745,
"status": "bugfix",
"first_release": "2025-10-07",
"end_of_life": "2030-10",
"release_manager": "Hugo van Kemenade"
}
}
python-releases.json
--------------------
A more complete JSON document of all Python releases since version 1.6 is
available at https://peps.python.org/api/python-releases.json and includes
metadata about each feature release cycle, for example:
.. code-block:: json
{
"metadata": {
"3.14": {
"pep": 745,
"status": "bugfix",
"branch": "3.14",
"release_manager": "Hugo van Kemenade",
"start_of_development": "2024-05-08",
"feature_freeze": "2025-05-07",
"first_release": "2025-10-07",
"end_of_bugfix": "2027-10-07",
"end_of_life": "2030-10-01"
}
}
}
And also detailed information about each individual release within that cycle,
for example:
.. code-block:: json
{
"releases": {
"3.14": [
{
"stage": "3.14.0 candidate 3",
"state": "actual",
"date": "2025-09-18",
"note": ""
},
{
"stage": "3.14.0 final",
"state": "actual",
"date": "2025-10-07",
"note": ""
},
{
"stage": "3.14.1",
"state": "expected",
"date": "2025-12-02",
"note": ""
}
]
}
}
release-schedule.ics
--------------------
An iCalendar file of Python release dates is available at
https://peps.python.org/release-schedule.ics.