mirror of
https://github.com/django/django.git
synced 2025-11-02 21:03:53 +00:00
Fixed #9523 -- Restart runserver after translation MO files change
Thanks to Krzysztof Kulewski for the initial patch.
This commit is contained in:
parent
090315f5df
commit
c3936c0d79
7 changed files with 82 additions and 5 deletions
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
^^^^^^
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue