-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.6 #1081
Comments
I am in favor. Anyone against? |
According to I agree that it is worth doing. Python 3.5 I'm not so sure if the tiny benefits outweigh the decreased support. I don't really mind though. For completeness, here are some PyPI stats from the last 30 days:
|
Sounds good to me. |
Revert this change when implement Zulko#1081
With the merging of #1106, this PR can now be closed. |
I've been working in a couple of refactors and I feel it's time to stop supporting both python 2.7 and python 3.5, and ensure support to python 3.7 (see #1018), 3.8 and any new python release in the future.
As you may know, python2.7 reaches its end-of-life date starting 2020, and 3.5's one is the next september. Several of the most relevant libraries of the python ecosystem (e.g, django and numpy, just to mention few) are already python3 only since a while.
This would simplify the code and the tests a bit (not a big deal, to be sincere), but most importantly, it'll allow us to start using new idioms/features of the language without hacks, conditional requirements, etc.
The text was updated successfully, but these errors were encountered: