documentation: apps without models.py can register for db related signals
|Reported by:||Val Neekman||Owned by:||donjpacheco|
|Severity:||Normal||Keywords:||apps without models database signals|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Before Django 1.7, all apps in the INSTALLED_APPS required to have a models.py, and they could latch onto the database related signals such as the pre_syncdb and the post_syncdb. So the documentations didn't need to be specific.
However, with the introduction of the AppConfig, apps no longer required a models.py and hence the documentation could benefit from an extra line of explanation that ONLY the apps that have the models.py could register to the database related signals.
"It may be None if the application doesn’t contain a models module."
Could be changed to:
"It may be None if the application doesn’t contain a models module. Please note that only applications with a models module can register for the database related signals such as pre_migrate / post_migrate signals.