summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-04-19 15:00:57 -0400
committerChris McDonough <chrism@plope.com>2011-04-19 15:00:57 -0400
commitdb51c08cda155ae5d9921c62700ab813f58f5d72 (patch)
treec22e331e99dcf9d3114d615e33a20e8a4e5a31c2
parentd3d17a21236ab0f3f1de52bd6bbde3eb3f045643 (diff)
downloadpyramid-db51c08cda155ae5d9921c62700ab813f58f5d72.tar.gz
pyramid-db51c08cda155ae5d9921c62700ab813f58f5d72.tar.bz2
pyramid-db51c08cda155ae5d9921c62700ab813f58f5d72.zip
rendering
-rw-r--r--CHANGES.txt10
1 files changed, 7 insertions, 3 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index affacb7d4..092423bc1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -32,9 +32,13 @@ Features
object (e.g. ``request.response`` within a view) now produces a new
``pyramid.response.Response`` object. This feature is meant to be used
mainly when a view configured with a renderer needs to set response
- attributes, but it can be used by any code to produce a response object
- (although the response object produced must still be returned unless a
- renderer is used).
+ attributes: all renderers will use the Response object implied by
+ ``request.response`` as the response object returned to the router.
+
+ ``request.response`` can also be used by code in a view that does not use a
+ renderer, however the response object that is produced by
+ ``request.response`` must be returned when a renderer is not in play (it is
+ not a "global" response).
- Integers and longs passed as ``elements`` to ``pyramid.url.resource_url``
or ``pyramid.request.Request.resource_url`` e.g. ``resource_url(context,