#26278 closed Bug (fixed)
Misleading documentation of apps.ready condition
Reported by: | Petr Dlouhý | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.9 |
Severity: | Normal | Keywords: | appconfig |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
From the discussion on django fieldsignals page it is clear, that the documentation about AppConfig.ready()
and apps.ready
variable could be quite misleading.
On https://docs.djangoproject.com/en/1.9/ref/applications/#django.apps.apps.ready in section about apps.ready
is written:
Boolean attribute that is set to True when the registry is fully populated.
And in the section about AppConfig.ready()
:
It is called as soon as the registry is fully populated.
Which might lead to conclusion, that apps.ready
variable is True
in AppConfig.ready()
, which is not true (as could be seen in Django code).
Note:
See TracTickets
for help on using tickets.
Is this better?