#26278: Misleading documentation of apps.ready condition
-------------------------------+-----------------------
Reporter: PetrDlouhy | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords: appconfig
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-----------------------
From the discussion on [https://github.com/craigds/django-
fieldsignals/commit/8607a699b5267a8f5e6caccb832324f6aecf00a2#diff-
a962eb2c68e7bee41e1dadef0d1bb42fR24 django fieldsignals page] it is clear,
that the
[https://docs.djangoproject.com/en/1.9/ref/applications/#django.apps.apps.ready
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
[https://github.com/django/django/blob/master/django/apps/registry.py#L114
Django code]).
--
Ticket URL: <https://code.djangoproject.com/ticket/26278>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.7301e28a4e4597990fba88644f186de6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
