summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-04-18 23:43:04 -0400
committerChris McDonough <chrism@plope.com>2011-04-18 23:43:04 -0400
commit524736e40cf709c64fd6568122e9d8489dcb2343 (patch)
tree777a3ebdae0dcf6455418290bb6c474c41f0e3bb /CHANGES.txt
parentdad904380fd3f53a82e5c48316cc0e7bfa199b74 (diff)
parentd07e169f89ead3ce41ae35a6c30df2964685c93e (diff)
downloadpyramid-524736e40cf709c64fd6568122e9d8489dcb2343.tar.gz
pyramid-524736e40cf709c64fd6568122e9d8489dcb2343.tar.bz2
pyramid-524736e40cf709c64fd6568122e9d8489dcb2343.zip
Merge branch 'requestresponse'
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt33
1 files changed, 33 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 66103fbc1..83d71e2b7 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,6 +1,39 @@
Next release
============
+Requestresponse branch
+----------------------
+
+- Deprecated all assignments to ``request.response_*`` attributes (for
+ example ``request.response_content_type = 'foo'`` is now deprecated).
+ Assignments and mutations of the following assignable request attributes
+ that were considered by the framework for response influence are now
+ deprecated: ``response_content_type``, ``response_headerlist``,
+ ``response_status``, ``response_charset``, and ``response_cache_for``.
+ Instead of assigning these to the request object for later detection by the
+ rendering machinery, users should use the appropriate API of the Response
+ object created by accessing ``request.response`` (e.g. code which does
+ ``request.response_content_type = 'abc'`` should be changed to
+ ``request.response.content_type = 'abc'``).
+
+- A custom request factory is now required to return a response object that
+ has a ``response`` attribute (or "reified"/lazy property) if they the
+ request is meant to be used in a view that uses a renderer. This
+ ``response`` attribute should be an instance of the class
+ ``pyramid.response.Response``.
+
+- The JSON and string renderer factories now assign to
+ ``request.response.content_type`` rather than
+ ``request.response_content_type``. Each renderer factory adetermines
+ whether it should change the content type of the response by comparing the
+ response's content type against the response's default content type; if the
+ content type is not the default content type (usually ``text/html``), the
+ renderer changes the content type (to ``application/json`` or
+ ``text/plain`` for JSON and string renderers respectively).
+
+- Made it possible to assign to and delete
+ ``pyramid.testing.DummyRequest.registry`` (bugfix).
+
Documentation
-------------