Most pluggable applications define an AppConfig subclass in an apps.py submodule. Many define a default_app_config variable pointing to this class in their __init__.py.
When the apps.py submodule exists and defines a single AppConfig subclass, Django now uses that configuration automatically, so you can remove default_app_config.
Does this make django-appconf redundant for Django 3.2+?
The Django 3.2 release notes describe the following new feature:
Does this make
django-appconf
redundant for Django 3.2+?