-
Notifications
You must be signed in to change notification settings - Fork 948
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for Python 3.9 #2008
Conversation
Let's wait until after 2.3 is released, all major scientific packages still support 3.9 and we don't have a pressing reason to drop it. |
This is to enable the process of the cythonization of space.py and time.py.
What are the planned new features in 2.3.0 that you think users of Python 3.9 really need to have? |
Right, this is an actual reason for us to drop 3.9. We pushed a lot of experimental stuff in 2.2, I would like to end 3.9 on a bit more stable platform. On the other hand we can always issue more patch releases. Let's say we would target 2.3 mid-way February. Immediately after we drop 3.9 support. Would that work for you, or would that significantly slow down development? |
Yeah, stability concern is not a real blocker given the patch releases.
SGTM |
for more information, see https://pre-commit.ci
I am running into 3.9 vs 3.10 now as well. I can fix the type annotations in #1994 to make it work with 3.9 or first move to 3.10, so I don't need to do the tedious work of fixing all type annotations (and then changing them back to 3.10 syntax). |
I am fine with dropping support for 3.9 soonish, but I think we still shouldn't immediately make mesa incompatible with 3.9 just for the sake of it. If there a good 3.10+ features that we want to use, we should not hesitate. But I don't think slightly nicer mypy syntax qualifies. |
Now that Mesa 2.3 is branched, and 3.0 development is started, we can drop Python 3.9 and require 3.10+ if we want. |
#2003 (comment)