Fixed #9523 -- Restart runserver after translation MO files change

Thanks to Krzysztof Kulewski for the initial patch.

2 files changed, 9 insertions, 2 deletions

diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 6bb03347c9..c301c5f094 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -791,8 +791,12 @@ Django.)
 
 The development server automatically reloads Python code for each request, as
 needed. You don't need to restart the server for code changes to take effect.
-However, some actions like adding files or compiling translation files don't
-trigger a restart, so you'll have to restart the server in these cases.
+However, some actions like adding files don't trigger a restart, so you'll 
+have to restart the server in these cases.
+
+.. versionchanged:: 1.7
+
+    Compiling translation files now also restarts the development server.
 
 If you are using Linux and install `pyinotify`_, kernel signals will be used to
 autoreload the server (rather than polling file modification timestamps each
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index 9a7ff41cf7..7218bcec22 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -346,6 +346,9 @@ Management Commands
 * The :djadmin:`runserver` command now uses ``inotify`` Linux kernel signals
   for autoreloading if ``pyinotify`` is installed.
 
+* The :djadmin:`runserver` command is now restarted when a translation file is
+  changed.
+
 Models
 ^^^^^^