nope. return and raise are handled differently. i ran into it while writing my cookie xfer module
there's an illustration of the difference here: https://github.com/jvanasco/pyramid_subscribers_cookiexfer i also brought it up in a discussion on this group once before. you'd have to inspect the objects in a subscriber , but the general notion was that on a "return", you are passing back a request object that you control, and pyramid will note the exception and act accordingly. if you raise the error, the request or response object is lost ( i don't recall which one ) and pyramid only really has the caught exception to handle. anyways, for general compatabilty reasons , i'd strongly suggest returning http exceptions instead of raising them. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
