summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2016-11-19 15:54:49 -0600
committerMichael Merickel <michael@merickel.org>2016-11-20 17:20:15 -0600
commit067ce0528a4c108e502c968b0865d213dbdda271 (patch)
tree2119c8387cfd08eaa0b2357d2eba1045726424e0 /CHANGES.txt
parent1644efffa25dcc70c9e01f709fbd203351e2f6ba (diff)
downloadpyramid-067ce0528a4c108e502c968b0865d213dbdda271.tar.gz
pyramid-067ce0528a4c108e502c968b0865d213dbdda271.tar.bz2
pyramid-067ce0528a4c108e502c968b0865d213dbdda271.zip
add changes for #2805
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt23
1 files changed, 23 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index a0a928f83..dac61678d 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -93,6 +93,29 @@ Features
using the ``PYRAMID_CSRF_TRUSTED_ORIGINS`` environment variable similar to
other settings. See https://github.com/Pylons/pyramid/pull/2823
+- ``pserve --reload`` now uses the
+ `hupper <http://docs.pylonsproject.org/projects/hupper/en/latest/>`
+ library to monitor file changes. This comes with many improvements:
+
+ - If the `watchdog <http://pythonhosted.org/watchdog/>`_ package is
+ installed then monitoring will be done using inotify instead of
+ cpu and disk-intensive polling.
+
+ - The monitor is now a separate process that will not crash and starts up
+ before any of your code.
+
+ - The monitor will not restart the process after a crash until a file is
+ saved.
+
+ - The monitor works on windows.
+
+ - You can now trigger a reload manually from a pyramid view or any other
+ code via ``hupper.get_reloader().trigger_reload()``. Kind of neat.
+
+ - You can trigger a reload by issuing a ``SIGHUP`` to the monitor process.
+
+ See https://github.com/Pylons/pyramid/pull/2805
+
Bug Fixes
---------