Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Drop Python2 support as part of 2.x release? #1927

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.

Sign up for GitHub

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

Jump to bottom
Closed
jeffwidman opened this issue Oct 11, 2019 · 2 comments
Closed

Drop Python2 support as part of 2.x release? #1927

jeffwidman opened this issue Oct 11, 2019 · 2 comments
Labels
packaging
Milestone
2.0

Comments

@jeffwidman
Copy link
Contributor

jeffwidman commented Oct 11, 2019 •
edited
Loading

I realize that many production environments have not migrated to python 3, and normally I would prefer to be the laggard here. However, the timing seems to line up really nicely for dropping python 2 support in the first 2.x release since it coincides with both our release cycle and the deprecation timeline of python 2:

  • The official death date of python 2 is Dec 31. Many popular open source libs in the python community are already dropping python2 support left, right, and center: https://python3statement.org
  • Given our historical rate of releases, it would not be tremendously out of character for us to wait to cut the next release until Jan 1, 2020. And I would not be opposed to doing it earlier... there's nothing magical about Jan 1, 2020.
  • We already need to bump up to 2.0 since I merged Remove old SimpleClient / SimpleProducer / SimpleConsumer #1196.

Plus, we aren't tying anyone's hands... if they still need a python 2 compatible version they can continue to use 1.4.7... it seems to be relatively stable after many, many iterations in the 1.4.x series.
@jeffwidman jeffwidman added this to the 2.0 milestone Oct 11, 2019
@dpkp
Copy link
Owner

dpkp commented Dec 29, 2019

I don't feel like maintaining py2 + py3 compatibility has been much of a burden for this library. I would prefer to keep compatibility.

This was referenced Feb 12, 2020
Open
Closed
@wbarnha
Copy link
Contributor

wbarnha commented Aug 5, 2023

GitHub runners no longer support Python 2.7, so we can't even test for 2.7 support anymore. I think it's time we do one final release and someone manually tests for 2.7 support, then set the minimum version to 3.8.

@cdce8p cdce8p mentioned this issue Aug 22, 2023
Closed
32 tasks
@cdce8p cdce8p mentioned this issue Oct 10, 2023
Merged
28 tasks
@dpkp dpkp closed this as completed Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
packaging
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
3 participants
@jeffwidman @dpkp @wbarnha