-
Notifications
You must be signed in to change notification settings - Fork 301
django-polymorphic now does support Django>3.0 #803
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
Comments
Django Polymorphhic 3.0 now supports Django 3.0 but drops 1.11. Looks like it's time to drop 1.11.... |
Dropping support for Django 1.11 is certainly good as it is end of life. However dropping of Django 1.11 support would mean another major release as it drops backwards compatibility. That's totally fine but I would like to combine it with adding support for DRF 3.12 as well. Hope this is coming out soon but I guess we won't release before it is not released. |
@sliverc yep. I took the opportunity to create a 3.3.0 milestone. |
we are following semver (unlike DRF) so it should be version |
I don't use polymorphic but noticed that the docs build was failing with this traceback:
I worked around this by forcing
Django>=2.2,<3.0
to get the docs built. PR coming shortly.The text was updated successfully, but these errors were encountered: