Fixed #22688 -- Documented ready() may be called more than once
This commit is contained in:
parent
63fc91b3ca
commit
b8fc167b32
|
@ -238,6 +238,15 @@ Methods
|
||||||
separate from the production settings, ``manage.py test`` would still
|
separate from the production settings, ``manage.py test`` would still
|
||||||
execute some queries against your **production** database!
|
execute some queries against your **production** database!
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
In the usual initialization process, the ``ready`` method is only called
|
||||||
|
once by Django. But in some corner cases, particularly in tests which
|
||||||
|
are fiddling with installed applications, ``ready`` might be called more
|
||||||
|
than once. In that case, either write idempotents methods, or put a flag
|
||||||
|
on your ``AppConfig`` classes to prevent re-running code which should
|
||||||
|
be executed exactly one time.
|
||||||
|
|
||||||
.. _namespace package:
|
.. _namespace package:
|
||||||
|
|
||||||
Namespace packages as apps (Python 3.3+)
|
Namespace packages as apps (Python 3.3+)
|
||||||
|
|
Loading…
Reference in New Issue