- Remove IResponder abstraction in favor of more general IResponse

  abstraction.

- It is now possible to return an arbitrary object from a Pyramid view
  callable even if a renderer is not used, as long as a suitable adapter to
  ``pyramid.interfaces.IResponse`` is registered for the type of the returned
  object.  See the section in the Hooks chapter of the documentation entitled
  "Changing How Pyramid Treats View Responses".

- The Pyramid router now, by default, expects response objects returned from
  view callables to implement the ``pyramid.interfaces.IResponse`` interface.
  Unlike the Pyramid 1.0 version of this interface, objects which implement
  IResponse now must define a ``__call__`` method that accepts ``environ``
  and ``start_response``, and which returns an ``app_iter`` iterable, among
  other things.  Previously, it was possible to return any object which had
  the three WebOb ``app_iter``, ``headerlist``, and ``status`` attributes as
  a response, so this is a backwards incompatibility.  It is possible to get
  backwards compatibility back by registering an adapter to IResponse from
  the type of object you're now returning from view callables.  See the
  section in the Hooks chapter of the documentation entitled "Changing How
  Pyramid Treats View Responses".

- The ``pyramid.interfaces.IResponse`` interface is now much more extensive.
  Previously it defined only ``app_iter``, ``status`` and ``headerlist``; now
  it is basically intended to directly mirror the ``webob.Response`` API,
  which has many methods and attributes.

- Documentation changes to support above.

1 files changed, 16 insertions, 3 deletions

diff --git a/TODO.txt b/TODO.txt
index 4b82208bd..ca2433d3c 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -6,14 +6,27 @@ Must-Have
 
 - To subclass or not subclass http exceptions.
 
-- Depend on only __call__ interface or only 3-attr interface in builtin code
-  that deals with response objects.
+- Flesh out IResponse interface.  Attributes Used internally: unicode_body /
+  body / content_type / charset / cache_expires / headers/
+  default_content_type / set_cookie / headerlist / app_iter / status /
+  __call__.
 
-- Figure out what to do with ``is_response``.
+- Deprecate view.is_response?
+
+- Move is_response to response.py?
+
+- 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.
 
+- Deprecate response_foo attrs on request at attribute set time rather than
+  lookup time.
+
 Should-Have
 -----------