From eb7ea411bfce55085449b79ac88aac19af0e232f Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Mon, 6 Sep 2010 00:06:48 +0000 Subject: - The ``repoze.bfg.interfaces.INewResponse`` interface now includes a ``request`` attribute; as a result, a handler for INewResponse now has access to the request which caused the response. - The INewResponse event is now not sent to listeners if the response returned by view code (or a renderer) is not a "real" response (e.g. if it does not have ``.status``, ``.headerlist`` and ``.app_iter`` attribtues). --- CHANGES.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index 1228ef4aa..bddef2b4f 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -9,6 +9,10 @@ Features ``repoze.bfg.request`` API chapter. It can be used to influence response values before a concrete response object has been created. +- The ``repoze.bfg.interfaces.INewResponse`` interface now includes a + ``request`` attribute; as a result, a handler for INewResponse now + has access to the request which caused the response. + - Each of the follow methods of the Configurator now allow the below-named arguments to be passed as "dotted name strings" (e.g. "foo.bar.baz") rather than as actual implementation objects @@ -85,6 +89,9 @@ Documentation new ``repoze.bfg.request`` API chapter. Some content was moved from this chapter into the API documentation itself. +- Various changes to denote that Python dotted names are now allowed + as input to Configurator methods. + Internal -------- @@ -96,6 +103,10 @@ Internal ``repoze.bfg.request.Request.add_response_callback`` takes its place. +- The ``repoze.bfg.events.NewResponse`` class's construct has changed: + it now must be created with ``(request, response)`` rather than + simply ``(response)``. + 1.3a9 (2010-08-22) ================== -- cgit v1.2.3