Fixed #9722 - used pyinotify as change detection system when available

Used pyinotify (when available) to replace the "pool-every-one-second"
mechanism in `django.utils.autoreload`.

Thanks Chris Lamb and Pascal Hartig for work on the patch.

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 2d9dcd9920..6bb03347c9 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -794,6 +794,18 @@ 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.
 
+If you are using Linux and install `pyinotify`_, kernel signals will be used to
+autoreload the server (rather than polling file modification timestamps each
+second). This offers better scaling to large projects, reduction in response
+time to code modification, more robust change detection, and battery usage
+reduction.
+
+.. _pyinotify: https://pypi.python.org/pypi/pyinotify/
+
+.. versionadded:: 1.7
+
+    ``pyinotify`` support was added.
+
 When you start the server, and each time you change Python code while the
 server is running, the server will validate all of your installed models. (See
 the ``validate`` command below.) If the validator finds errors, it will print