summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2017-05-04 00:23:18 -0500
committerMichael Merickel <michael@merickel.org>2017-05-04 00:25:28 -0500
commite2e51b35303e69b5028a84026837095b1bfe6f79 (patch)
treee6c456d719aab68160ea6acdb8990f325cd43bc5 /CHANGES.txt
parentba677d566e86545ec46920d1a1279aade14ae70e (diff)
downloadpyramid-e2e51b35303e69b5028a84026837095b1bfe6f79.tar.gz
pyramid-e2e51b35303e69b5028a84026837095b1bfe6f79.tar.bz2
pyramid-e2e51b35303e69b5028a84026837095b1bfe6f79.zip
add changelog for #3031
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt7
1 files changed, 6 insertions, 1 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index b299ed6e9..80b5003c1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -125,11 +125,16 @@ Backward Incompatibilities
``request.exception`` and ``request.exc_info`` themselves to indicate
the exception that was squashed when generating the response.
+ Similar behavior occurs with ``request.invoke_exception_view`` in which
+ the exception properties are set to reflect the exception if a response
+ is successfully generated by the method.
+
This is a very minor incompatibility. Most tweens right now would give
priority to the raised exception and ignore ``request.exception``. This
change just improves and clarifies that bookkeeping by trying to be
more clear about the relationship between the response and its squashed
- exception. See https://github.com/Pylons/pyramid/pull/3029
+ exception. See https://github.com/Pylons/pyramid/pull/3029 and
+ https://github.com/Pylons/pyramid/pull/3031
Documentation Changes
---------------------