Skip to content
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

Closed
simonzhaoms opened this issue Feb 11, 2022 · 9 comments
Closed

[ASK] Whether to drop support for Python 3.6 #1638

simonzhaoms opened this issue Feb 11, 2022 · 9 comments
Labels
help wanted Need help from developers

Comments

@simonzhaoms
Copy link
Collaborator

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:

@simonzhaoms simonzhaoms added the help wanted Need help from developers label Feb 11, 2022
@loomlike
Copy link
Collaborator

3.6 is still the most popular version:
https://w3techs.com/technologies/details/pl-python/3

but I agree that it's a good time to start thinking about migration.
Maybe start running test/build pipelines for both 3.6 and 3.8 for a while and eventually drop 3.6?

@simonzhaoms
Copy link
Collaborator Author

As of March 8, 2022:
Screen Shot 2022-03-08 at 8 49 44 AM
Let's see what it will be in 1 month, 2 months, 6 months.

@simonzhaoms
Copy link
Collaborator Author

April 8, 2022:
Screenshot from 2022-04-08 14-39-25

@simonzhaoms
Copy link
Collaborator Author

Screenshot from 2022-05-11 15-14-50

@AdityaSoni19031997
Copy link
Contributor

AdityaSoni19031997 commented Oct 16, 2022

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+.

@miguelgfierro
Copy link
Collaborator

Right now we are not testing on 3.6, I think still most of the code works, but not 100% sure

@miguelgfierro
Copy link
Collaborator

image

As of Oct 2022

@miguelgfierro
Copy link
Collaborator

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?

@simonzhaoms
Copy link
Collaborator Author

@miguelgfierro Yeah, let's keep it for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Need help from developers
Projects
None yet
Development

No branches or pull requests

4 participants