diff options
| author | Claude Paroz <claude@2xlibre.net> | 2014-05-24 15:57:04 +0200 |
|---|---|---|
| committer | Claude Paroz <claude@2xlibre.net> | 2014-05-24 15:58:57 +0200 |
| commit | b8fc167b32926e09d6d73eddc555343360f9c087 (patch) | |
| tree | 3debaade7398491590b8e27a622948881a8c2372 /docs | |
| parent | 63fc91b3cac523690655c1d86d09972e0cc3a29d (diff) | |
Fixed #22688 -- Documented ready() may be called more than once
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/applications.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt index 829e273aa9..fa69a28493 100644 --- a/docs/ref/applications.txt +++ b/docs/ref/applications.txt @@ -238,6 +238,15 @@ Methods separate from the production settings, ``manage.py test`` would still 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 packages as apps (Python 3.3+) |
