-
Notifications
You must be signed in to change notification settings - Fork 475
when do we drop support for python 3.6? #2350
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
Comments
Ooh. Let's make |
Or even |
having not heard any objections, I will assume nobody is still interested in extending support for Python 3.6 so I propose we make the next release the last one that supports 3.6 and require 3.7 from the one following. |
Just a reminder to update the README when the change happens. |
I suggest following NEP 29 for dependency bumps. |
3.10 is out next week, while 3.6 reaches end of life by the end of this year. It's time to require 3.7 or greater, so we can finally use built-in dataclasses and more. Fixes #2350
python 3.6 (released 5 years ago) officially reaches end of life at the end of this year, python 3.10 is in beta (stable is due around october).
It would be nice to be able to depend on python3.7+ only features like dataclasses, customization of module attributes, better typing, dict always ordered, etc.
I propose we drop python 3.6 by the time 3.10 reaches stable (sometime in autumn), if not even earlier.
Is anybody still using python 3.6 who would prefer to extend this further?
The text was updated successfully, but these errors were encountered: