- New method named ``pyramid.request.Request.is_response``. This method

  should be used instead of the ``pyramid.view.is_response`` function, which
  has been deprecated.

- Deprecated ``pyramid.view.is_response`` function in favor of (newly-added)
  ``pyramid.request.Request.is_response`` method.  Determining if an object
  is truly a valid response object now requires access to the registry, which
  is only easily available as a request attribute.  The
  ``pyramid.view.is_response`` function will still work until it is removed,
  but now may return an incorrect answer under some (very uncommon)
  circumstances.

1 files changed, 12 insertions, 0 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index c7ca3794d..ea4bedc7e 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -140,6 +140,10 @@ Features
   among other things, the ``conditional_response`` feature of WebOb response
   objects will now behave properly.
 
+- New method named ``pyramid.request.Request.is_response``.  This method
+  should be used instead of the ``pyramid.view.is_response`` function, which
+  has been deprecated.
+
 Bug Fixes
 ---------
 
@@ -270,6 +274,14 @@ Deprecations
   1.0 and before).  In a future version, these methods will be removed
   entirely.
 
+- Deprecated ``pyramid.view.is_response`` function in favor of (newly-added)
+  ``pyramid.request.Request.is_response`` method.  Determining if an object
+  is truly a valid response object now requires access to the registry, which
+  is only easily available as a request attribute.  The
+  ``pyramid.view.is_response`` function will still work until it is removed,
+  but now may return an incorrect answer under some (very uncommon)
+  circumstances.
+
 Behavior Changes
 ----------------