diff options
| author | Michael Merickel <michael@merickel.org> | 2015-02-06 13:03:20 -0600 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2015-02-06 13:03:20 -0600 |
| commit | 04206845591cb5af1038a29f6e943bfb169c2d5c (patch) | |
| tree | 80d3a9a1b0b7bdb23b873a1c04811b55d90184f7 | |
| parent | 72bf6bb1b942a56a39d5ae33634e7aa8fac7080a (diff) | |
| download | pyramid-04206845591cb5af1038a29f6e943bfb169c2d5c.tar.gz pyramid-04206845591cb5af1038a29f6e943bfb169c2d5c.tar.bz2 pyramid-04206845591cb5af1038a29f6e943bfb169c2d5c.zip | |
update changelog
| -rw-r--r-- | CHANGES.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 30f30cec7..a02ae504b 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -81,14 +81,18 @@ Features Python 3. See https://github.com/Pylons/pyramid/pull/1556 - ``request.response`` will no longer be mutated when using the - ``pyramid.renderers.render_to_response()`` API. Almost all renderers + ``pyramid.renderers.render_to_response()`` API. It is now necessary to + pass in a ``response=`` argument to ``render_to_response`` if you wish to + supply the renderer with a custom response object for it to use. If you + do not pass one then a response object will be created using the + application's ``IResponseFactory``. Almost all renderers mutate the ``request.response`` response object (for example, the JSON renderer sets ``request.response.content_type`` to ``application/json``). However, when invoking ``render_to_response`` it is not expected that the response object being returned would be the same one used later in the request. The response object returned from ``render_to_response`` is now explicitly different from ``request.response``. This does not change the - API of a renderers. See https://github.com/Pylons/pyramid/pull/1563 + API of a renderer. See https://github.com/Pylons/pyramid/pull/1563 Bug Fixes --------- |