From da235c9a8469b1fe813c1e51593e6b915892eb6a Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Mon, 4 Nov 2013 23:28:38 +0100 Subject: [PATCH] Improved changelog for runserver in 1.7. --- docs/releases/1.7.txt | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 802d16cc5c6..1bf93468ef2 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -343,11 +343,20 @@ Management Commands Django takes this information from your settings file. If you have configured multiple caches or multiple databases, all cache tables are created. -* The :djadmin:`runserver` command now uses ``inotify`` Linux kernel signals - for autoreloading if ``pyinotify`` is installed. +* The :djadmin:`runserver` command received several improvements: -* The :djadmin:`runserver` command is now restarted when a translation file is - changed. + * On BSD systems, including OS X, the development server will reload + immediately when a file is changed. Previously, it was polling the + filesystem for changes every second. That caused a small delay before + reloads and reduced battery life on laptops. + + * On Linux, the same improvements are available when pyinotify_ is + installed. + + .. _pyinotify: https://pypi.python.org/pypi/pyinotify + + * Besides, the development server automatically reloads when a translation + file is updated, ie. after running :djadmin:`compilemessages`. Models ^^^^^^