diff options
| author | Michael Merickel <michael@merickel.org> | 2013-09-05 23:22:35 -0500 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2013-09-05 23:22:35 -0500 |
| commit | fbdc3a01842e9067478dbf95ba8cde4e31bbb174 (patch) | |
| tree | 1c17d3a2c615f8e6ca18f7872102a205c0581ada | |
| parent | 027c9809ca9377b3ae37a34e4ed997d8fdfddfb8 (diff) | |
| download | pyramid-fbdc3a01842e9067478dbf95ba8cde4e31bbb174.tar.gz pyramid-fbdc3a01842e9067478dbf95ba8cde4e31bbb174.tar.bz2 pyramid-fbdc3a01842e9067478dbf95ba8cde4e31bbb174.zip | |
s/view execution machinery/generating a response/
| -rw-r--r-- | CHANGES.txt | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 7d06999d6..6392c7b3b 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -10,11 +10,10 @@ Backwards Incompatibilities - ``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()``. + ``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 generating a response; it was a bug + when it was done as a side effect of calling ``pyramid.renderers.render()``. 1.5a1 (2013-08-30) ================== |