- 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, 0 insertions, 12 deletions

diff --git a/TODO.txt b/TODO.txt
index 9d9bbf1eb..27ab9ffb5 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -6,18 +6,6 @@ Must-Have
 
 - To subclass or not subclass http exceptions.
 
-- Deprecate view.is_response?
-
-- Move is_response to response.py?
-
-- Create add_response_adapter Configurator API?
-
-- Make sure registering IResponse adapter for webob.Response doesn't make it
-  impossible to register an IResponse adapter for an interface that a
-  webob.Response happens to implement.
-
-- Run whatsitdoing tests.
-
 - Docs mention ``exception.args[0]`` as a way to get messages; check that
   this works.