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

Drop Python 2 support #801

Merged
merged 1 commit into from
Sep 11, 2019
Merged

Drop Python 2 support #801

merged 1 commit into from
Sep 11, 2019

Conversation

claudep
Copy link
Contributor

@claudep claudep commented Sep 10, 2019

No description provided.

@claudep
Copy link
Contributor Author

claudep commented Sep 10, 2019

This will be mandatory to support Django 3.0 (unless we add more compatiblity shims).

@etianen etianen merged commit 83a33e5 into etianen:master Sep 11, 2019
@etianen
Copy link
Owner

etianen commented Sep 11, 2019

Very nice. I suspect there'll be a few more places where the code can be cleaned up without the requirement to support Python 2, Django < 3.0, but this is a great start.

I think that following Django's advice to drop Django <3.0 support and Python 2 probably merits a breaking release (v3.0?), so if there's anything else you can see that will cut out compatibility shims, I'd love a PR.

@claudep claudep deleted the droppy2 branch September 11, 2019 11:46
@claudep
Copy link
Contributor Author

claudep commented Sep 11, 2019

For now I didn't see yet a compelling reason to drop support for older Django version, but it might occur when adding support for Django 3.0.

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 this pull request may close these issues.

2 participants