> Have you tried "raise HTTPFound(location=url).exception" ? When you do > .exception it creates an exception object that has a __call__ method > that just dispatches to the response object's __call__ (i.e., it's still > an application).
I thought I tried that first thing, what seems to happen then is that pylons tries to set the headers on the exception, which blows up. And when I pull wsgi_response off of the exception, and return that, things get further up the pylons chain, but redirection still does not work. I think I need to sit down and try to make pylons work with 2.4 first, and then I can come back to tg. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
