diff options
| author | Michael Merickel <michael@merickel.org> | 2017-05-09 01:41:12 -0500 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2017-05-09 01:41:12 -0500 |
| commit | 1fc7eefc4ac9f5ea3d22d7a108cd3da1e73cbcfa (patch) | |
| tree | e6f76cce10e7048d632fd6a7156813bcb4d1be61 | |
| parent | d1745247edae01ef934acf5bb206d29952a99dbf (diff) | |
| download | pyramid-1fc7eefc4ac9f5ea3d22d7a108cd3da1e73cbcfa.tar.gz pyramid-1fc7eefc4ac9f5ea3d22d7a108cd3da1e73cbcfa.tar.bz2 pyramid-1fc7eefc4ac9f5ea3d22d7a108cd3da1e73cbcfa.zip | |
fix changelog, added #3031 and #3029 to the wrong release version
| -rw-r--r-- | CHANGES.txt | 47 |
1 files changed, 25 insertions, 22 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 80b5003c1..51a1e457d 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,3 +1,28 @@ +1.9a2 (2017-05-09) +================== + +Backward Incompatibilities +-------------------------- + +- ``request.exception`` and ``request.exc_info`` will only be set if the + response was generated by the EXCVIEW tween. This is to avoid any confusion + where a response was generated elsewhere in the pipeline and not in + direct relation to the original exception. If anyone upstream wants to + catch and render responses for exceptions they should set + ``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 and + https://github.com/Pylons/pyramid/pull/3031 + 1.9a1 (2017-05-01) ================== @@ -114,28 +139,6 @@ Deprecations See https://github.com/Pylons/pyramid/pull/2854 and https://github.com/Pylons/pyramid/pull/3019 -Backward Incompatibilities --------------------------- - -- ``request.exception`` and ``request.exc_info`` will only be set if the - response was generated by the EXCVIEW tween. This is to avoid any confusion - where a response was generated elsewhere in the pipeline and not in - direct relation to the original exception. If anyone upstream wants to - catch and render responses for exceptions they should set - ``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 and - https://github.com/Pylons/pyramid/pull/3031 - Documentation Changes --------------------- |