[1.6.x] Fixed #21210 -- Documented when runserver doesn't auto-restart.

Thanks gergely at polonkai.eu for the suggestion.

Backport of 9b7d38ed5a from master
This commit is contained in:
Bouke Haarsma 2013-10-14 14:19:02 +02:00 committed by Tim Graham
parent e3c8db61f3
commit da181056a9
2 changed files with 10 additions and 0 deletions

View File

@ -182,6 +182,14 @@ It worked!
Full docs for the development server can be found in the Full docs for the development server can be found in the
:djadmin:`runserver` reference. :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 Database setup
-------------- --------------

View File

@ -732,6 +732,8 @@ Django.)
The development server automatically reloads Python code for each request, as 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. 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 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 server is running, the server will validate all of your installed models. (See