diff options
| author | Michael Merickel <michael@merickel.org> | 2017-05-04 00:27:18 -0500 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2017-05-04 00:27:18 -0500 |
| commit | d1745247edae01ef934acf5bb206d29952a99dbf (patch) | |
| tree | 3c48cd2cc82dfe3351f8331559388ab5345d8ecc /docs/whatsnew-1.9.rst | |
| parent | ab8c57811d904377416c2786670ecf0e81d8ca33 (diff) | |
| download | pyramid-d1745247edae01ef934acf5bb206d29952a99dbf.tar.gz pyramid-d1745247edae01ef934acf5bb206d29952a99dbf.tar.bz2 pyramid-d1745247edae01ef934acf5bb206d29952a99dbf.zip | |
line length
Diffstat (limited to 'docs/whatsnew-1.9.rst')
| -rw-r--r-- | docs/whatsnew-1.9.rst | 24 |
1 files changed, 5 insertions, 19 deletions
diff --git a/docs/whatsnew-1.9.rst b/docs/whatsnew-1.9.rst index f49258662..0ba29625c 100644 --- a/docs/whatsnew-1.9.rst +++ b/docs/whatsnew-1.9.rst @@ -49,25 +49,11 @@ Deprecations 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 - :meth:`pyramid.request.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 +- ``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 :meth:`pyramid.request.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 Enhancements -------------------------- |