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

Dropping Python 2 Support #179

Open
isidentical opened this issue Apr 21, 2020 · 3 comments · May be fixed by #229
Open

Dropping Python 2 Support #179

isidentical opened this issue Apr 21, 2020 · 3 comments · May be fixed by #229

Comments

@isidentical
Copy link
Contributor

Is there any plan to drop python 2 support, and refactor some parts with assuming only 3.5+ usage (or better, 3.6+)

@berkerpeksag
Copy link
Owner

I think we can start supporting Python 3.6+ after one more bugfix release. We can also skip 0.9 and bump to 1.0 (that would also mean dropping all of the deprecated APIs)

@isidentical
Copy link
Contributor Author

That'd make sense. Please let me know if there is anything I could do, (by the way if you need any help maintaing this library, it would be an amazing experience for me to collaborate with you).

@hugovk
Copy link

hugovk commented Jun 28, 2021

Is there a timetable for that last bugfix release before dropping EOL versions?

berkerpeksag added a commit that referenced this issue Jan 1, 2025
berkerpeksag added a commit that referenced this issue Jan 1, 2025
berkerpeksag added a commit that referenced this issue Jan 2, 2025
berkerpeksag added a commit that referenced this issue Jan 2, 2025
berkerpeksag added a commit that referenced this issue Jan 4, 2025
berkerpeksag added a commit that referenced this issue Jan 4, 2025
@berkerpeksag berkerpeksag linked a pull request Jan 7, 2025 that will close this issue
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants