id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
26278	Misleading documentation of apps.ready condition	Petr Dlouhý	nobody	"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])."	Bug	closed	Documentation	1.9	Normal	fixed	appconfig		Accepted	1	0	0	0	0	0