summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2013-09-05 23:59:45 -0400
committerChris McDonough <chrism@plope.com>2013-09-05 23:59:45 -0400
commit027c9809ca9377b3ae37a34e4ed997d8fdfddfb8 (patch)
tree4682cd488b8c78df6d4b4822e8af8499d6d4b5ac /CHANGES.txt
parentef5596c5e3de01afd1405e87f06de1f9867b4c86 (diff)
parent3803d92fc0da5282656d4229e063a1908ec5522a (diff)
downloadpyramid-027c9809ca9377b3ae37a34e4ed997d8fdfddfb8.tar.gz
pyramid-027c9809ca9377b3ae37a34e4ed997d8fdfddfb8.tar.bz2
pyramid-027c9809ca9377b3ae37a34e4ed997d8fdfddfb8.zip
resolve conflicts, reword change entry a bit
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 80578d539..7d06999d6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -8,6 +8,14 @@ Backwards Incompatibilities
have been deprecated since Pyramid 1.1, and as per the deprecation policy,
have now been removed.
+- ``request.response`` will no longer be mutated when using the
+ ``pyramid.renderers.render()`` API. Almost all renderers mutate the
+ ``request.response`` response object (for
+ example, the JSON renderer sets ``request.response.content_type`` to
+ ``application/json``), but this is only necessary when the renderer
+ is called by the view execution machinery; it was a bug when it was
+ done as a side effect of calling ``pyramid.renderers.render()``.
+
1.5a1 (2013-08-30)
==================