Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Drop python 3.7?

See original GitHub issue

🧰 Task

How does everyone feel about dropping python 3.7?

We had previously discussed following NEP29 which:

recommends that all projects across the Scientific Python ecosystem adopt a common “time window-based” policy for support of Python and NumPy versions.

with a proposed support table of

Date	Python	NumPy
Jul 26, 2021	3.7+	1.18+
Dec 22, 2021	3.7+	1.19+
Dec 26, 2021	3.8+	1.19+
Jun 21, 2022	3.8+	1.20+
Apr 14, 2023	3.9+	1.20+

with 3.8, we could get in on that sweet, sweet walrus operator, and functools.cached_property

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:11 (11 by maintainers)

Top GitHub Comments

3reactions

jnicommented, Jan 27, 2022

I think we could just drop 3.7 on 0.4.15? I don’t see this as a big reason to bump to 0.5. Then this doesn’t have to affect any of the other deprecations.

2reactions

tlambert03commented, Jan 26, 2022

I am fine both with releasing 0.5 just as a py3.7 drop, with 0.5.1 bringing all the other deprecations (as @potating-potato suggested), or just bringing all of our breaking changes together in 0.5.0. whatever the @napari/core-devs consensus is