-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[ASK] Whether to drop support for Python 3.6 #1638
Comments
3.6 is still the most popular version: but I agree that it's a good time to start thinking about migration. |
As of https://endoflife.date/python, Python 3.6 had already reached EOL 9 months before. Next best version for long term compatibility is Python 3.8+. |
Right now we are not testing on 3.6, I think still most of the code works, but not 100% sure |
We discussed this point. The approach we considered is, right now we are not getting problems with 3.6, and it is used by 40%, so we can keep it for now. If we start getting dependency issues, then we can reconsider removing 3.6. @simonzhaoms do you like this approach, or do you think we should change it? |
@miguelgfierro Yeah, let's keep it for now. |
Description
As said at Release Python 3.6, Python 3.6 has now reached end-of-life. I wonder if we should drop the support for Python 3.6 in the near future?
Other Comments
See also:
The text was updated successfully, but these errors were encountered: