From 5c1be8a870f9783c4164cf09b1e9db3205ad1f1e Mon Sep 17 00:00:00 2001 From: Bouke Haarsma Date: Mon, 14 Oct 2013 14:19:02 +0200 Subject: [PATCH] [1.5.x] Fixed #21210 -- Documented when runserver doesn't auto-restart. Thanks gergely at polonkai.eu for the suggestion. Backport of 9b7d38ed5a from master --- docs/intro/tutorial01.txt | 8 ++++++++ docs/ref/django-admin.txt | 2 ++ 2 files changed, 10 insertions(+) diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt index d9e8319170..8062f1cd59 100644 --- a/docs/intro/tutorial01.txt +++ b/docs/intro/tutorial01.txt @@ -181,6 +181,14 @@ It worked! Full docs for the development server can be found in the :djadmin:`runserver` reference. +.. admonition:: Automatic reloading of :djadmin:`runserver` + + 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. + Database setup -------------- diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 4552440394..07a7bb10eb 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -664,6 +664,8 @@ 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. 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