python version for 5.0

17 views
Skip to first unread message

Marten van Kerkwijk

unread,
May 6, 2021, 8:00:11 PM5/6/21
to astro...@googlegroups.com
Hi All,

Just thought I'd check what we think the minimum python version for 5.0
will be. Following NEP 29, we should support python versions for 42
months. For python 3.7, which was released end of June 2018, that would
mean until December 2021. Obviously, that is also roughly the time we
would release 5.0...

So, should we drop 3.7 for 5.0? Practically, it means we can drop the
importlib_metadata work-around, and start using the walrus. I think for
a LTS like 5.0, it makes sense to be fairly strict in our requirements,
since we have to support it for quite a while, so I'd go with >= 3.8.

Somewhat similarly, numpy we support for 2 years, and 1.18 was released
Dec 22, 2019 (and by Dec 2021, there likely will be a 1.21). So,
perhaps move up to 1.19 (if 1.21 exists)? Here, there is little
that will change; just a few NUMPY_LT_1_18 and NUMPY_LT_1_19 occurrences
that can be simplified.

All the best,

Marten

Thomas Robitaille

unread,
May 7, 2021, 5:07:24 AM5/7/21
to astro...@googlegroups.com
I am in favour of this!

Cheers,
Tom

--
You received this message because you are subscribed to the Google Groups "astropy-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to astropy-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/astropy-dev/87tunf9zw8.fsf%40weasel.astro.utoronto.ca.

Matt Craig

unread,
May 7, 2021, 9:40:18 AM5/7/21
to astropy-dev
Hi,

I also support these changes.

Matt


Adrian Price-Whelan

unread,
May 7, 2021, 10:13:53 AM5/7/21
to astro...@googlegroups.com
I think this sounds sensible!

best,
Adrian



--
Adrian M. Price-Whelan
Flatiron Institute, NYC
http://adrn.github.io
(he / him)
Reply all
Reply to author
Forward
0 new messages