Skip to content

Commit 41a76d6

Browse files
authored
Update APE10 to have higher minimum python 3 versions
Following discussion in astropy/astropy#6000: change the minimum version for python 3 such that the minimum python version will be supported for (most of) the lifetime of any astropy release.
1 parent b6f24c3 commit 41a76d6

1 file changed

Lines changed: 16 additions & 8 deletions

File tree

‎APE10.rst‎

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -90,12 +90,12 @@ versions:
9090
========== ===============================
9191
Version Minimum required Python version
9292
========== ===============================
93-
v2.0 - LTS Python 2.7 or Python 3.3+
94-
v3.0 Python 3.4+
95-
v3.1 Python 3.4+
96-
v3.2 Python 3.4+
97-
v3.3 Python 3.5+
98-
v4.0 - LTS Python 3.5+
93+
v2.0 - LTS Python 2.7 or Python 3.4+
94+
v3.0 Python 3.5+
95+
v3.1 Python 3.5+
96+
v3.2 Python 3.5+
97+
v3.3 Python 3.6+
98+
v4.0 - LTS Python 3.6+
9999
========== ===============================
100100

101101
Implementation
@@ -210,8 +210,8 @@ There are several benefits to following the plan proposed above:
210210

211211
* We will be able to start using Python 3-only features internally, including
212212
for example function annotations (e.g., for units), matrix multiplication
213-
(e.g., for coordinates; note that this will only be possible once we support
214-
only Python 3.5+)
213+
(e.g., for coordinates; note that this will only be possible with Python 3.5+,
214+
which in part drives that as minimum version for astropy 3.0)
215215

216216
* Since we will need to keep adding Python 3.x releases to the continuous
217217
integration over the coming years, we will at least be able to remove Python
@@ -256,3 +256,11 @@ feedback (some of which led to minor adjustments particularly regarding the PyPI
256256
issues). Because of this apparent support by the community and agreement from
257257
the coordination committee with the goals of this APE, it was accepted Aug 22,
258258
2016.
259+
260+
Updates after acceptance of the APE
261+
-----------------------------------
262+
In further discussions (https://github.com/astropy/astropy/issues/6000), it was
263+
noted that one should not aim to support versions of python that will reach end
264+
of life during the time an astropy version is supported. In particular, python
265+
3.3 would reach end-of-life only 3 months after the nominal astropy 2.0 release.
266+
Hence, all minimum versions of python 3 were increased by one minor version.

0 commit comments

Comments
 (0)