-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Remove default_app_config with change to only support Django 3.2+ #1741
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
See also 7b2e0d7#r78271539 for a missing piece.
@blueyed @phillipuniverse |
This is the correct fix from the change at django-extensions@7b2e0d7#r78148010
@ulgens I fixed the pragma linting, everything should be GTG now. |
Hello, guys, @phillipuniverse , @ulgens Thanks for supporting this. When do you think we could merge this and deploy? I am upgrading the django into 3.2 and stuck by this one when I run the pytest. Thanks |
I gave my approval but i don't have permission to merge. |
@bigshoesdev nothing more I can do on my side, this is the fix but a maintainer needs to approve the workflow and ultimately merge. |
@trbs ping 👋🏻 |
Thanks ! |
@trbs I think this was the last blocker for a new release with Django 4 support. Is there a plan for that release? If so, can we help? |
This is the correct fix from the change at 7b2e0d7#r78148010. Related to Django 3.2 minimum requirements added at #1730.
Also fixes deprecation warnings like: