@@ -74,11 +74,19 @@ a project with a major or minor version released in December 2019 should
74
74
support Python 3.6 and newer, and a project with a major or minor version
75
75
release in November 2020 should support Python 3.7 and newer.
76
76
77
- The current Python release cadence is 18 months so a 42 month window
78
- ensures that there will always be at least two minor versions of Python
79
- in the window. The window is extended 6 months beyond the anticipated two-release
80
- interval for Python to provide resilience against small fluctuations /
81
- delays in its release schedule.
77
+ When this NEP was drafted the Python release cadence was 18 months so a 42
78
+ month window ensured that there would always be at least two minor versions of
79
+ Python in the window. The window was extended 6 months beyond the anticipated
80
+ two-release interval for Python to provide resilience against small
81
+ fluctuations / delays in its release schedule.
82
+
83
+ The Python release cadence was increased to 12 months in `PEP 0602
84
+ <https://peps.python.org/pep-0602/> `__ so there will now be 3-4 Python releases
85
+ in the support window at any time. However, PEP 0602 does not decrease the
86
+ support window of Python (18 months of regular full bug-fix releases and 42
87
+ months of as-needed source-only releases). Thus, we do not expect
88
+ our users to upgrade Python faster, and our 42 month support window will
89
+ cover the same portion of the upstream support of any given Python release.
82
90
83
91
Because Python minor version support is based only on historical
84
92
release dates, a 42 month time window, and a planned project release
0 commit comments