This doesn't make much sense to me.
Wouldn't there be much more utility to have the response_callback AFTER the
response is created, this way it can operate on the response object?
I did some digging in the source, and came across this change:
https://github.com/Pylons/pyramid/commit/fc477b2e4b20ae2788e468e45b2831e774be8ced
and this issue:
https://github.com/Pylons/pyramid/issues/1116
So now it makes perfect sense.
It's probably worth discussing this in the docs near the "Response
Callbacks" and "NewResponse" sections.
Chris's text in the commit is perfect:
The ``pyramid.events.NewResponse`` event is now sent **after** response
callbacks are executed. It previously executed before response callbacks
were executed. Rationale: it's more useful to be able to inspect the
response after response callbacks have done their jobs instead of before.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
