From f50a17785cdb67bc9d1b146d01c731cb6bfc48cf Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 21 Jun 2014 15:00:35 +0200 Subject: [1.7.x] Fixed #8033 -- Explained app registry error during translation setup Thanks Tim Graham and Aymeric Augustin for the review. Backport of 9618d68b34 from master. --- docs/ref/applications.txt | 6 +++--- docs/releases/1.7.txt | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/ref/applications.txt b/docs/ref/applications.txt index 8052524a49..f944a6fcac 100644 --- a/docs/ref/applications.txt +++ b/docs/ref/applications.txt @@ -382,9 +382,9 @@ Troubleshooting Here are some common problems that you may encounter during initialization: -* ``RuntimeError: App registry isn't ready yet.`` This happens when importing - an application configuration or a models module triggers code that depends - on the app registry. +* ``AppRegistryNotReady`` This happens when importing an application + configuration or a models module triggers code that depends on the app + registry. For example, :func:`~django.utils.translation.ugettext()` uses the app registry to look up translation catalogs in applications. To translate at diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 3ab136d24b..a02bee3bcf 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -934,7 +934,7 @@ script with:: >>> import django >>> django.setup() -Otherwise, you will hit ``RuntimeError: App registry isn't ready yet.`` +Otherwise, you will hit an ``AppRegistryNotReady`` exception. App registry consistency ^^^^^^^^^^^^^^^^^^^^^^^^ -- cgit v1.3