On Jan 3, 2008 11:08 PM, Titus Brown <<a href="mailto:titus@caltech.edu">titus@caltech.edu</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Jan 03, 2008 at 03:54:35PM -0600, Ken Kuhlman wrote:<br>-> I've been trying to do a better job of testing my (turbogears) web apps<br><div class="Ih2E3d">-> lately, and am trying to decide if I should be using twill or
paste.fixture.<br>-> I like a lot of things about twill, but one of the key strengths of paste<br>-> (IMHO) is that it's "in process" testing feature includes the ability to<br>-> dump the wsgi environment (unlike wsgi_intercept, which otherwise is a very
<br>-> nice hack). Access to the environ is very handy [1] when you're doing MVC<br>-> work & trying to seperate what the controller's doing from what the rendered<br>-> result looks like.<br>-> Anyway, code speaks louder than words, so I've included an example of what
<br>-> I'd like to see, and a patch to twill to make it work. I'd be interested<br>-> to know if you all think I'm on the right track or if I'm all wet. I'm a<br>-> twill & wsgi n00b, so my apologies if I've missed anything obvious.
<br><br></div>Hey Ken! Good idea, and one that I think can be generalized nicely...<br>which is why I want to think about it a bit more before committing to<br>any one direction. We should include Kumar, too, because he's taken
<br>over wsgi_intercept - Kumar, are you on this list?<br><br>First, I don't want to include a default command that deals with WSGI,<br>because most people probably won't know what it is or use it. We could<br>still create an extension module, but there are some other questions...
<br></blockquote><div><br>Cool.. I figured this would be a first attempt. Extension module it is. <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>For example, you may want to have multiple WSGI apps in play, in which<br>case your global environ hack would cause problems. (This is why<br>_wsgi_intercept, which contains the apps, is the only global one.)<br><br>
And why not use middleware instead of a solid hook? Something like<br>this:<br><br>--<br># install 'simple_app' with an environment printer under 'foo_name'<br>app_fn = lambda: twill.wsgi.env_printer('foo_name', simple_app)
<br>twill.add_wsgi_intercept('localhost', 8001, lambda: app_fn)<br>--<br></blockquote><div><br>I was thinking that the global hack would only impact multiple wsgi_intercept calls, which would be less of a problem. I believe you when you say it's more than that, though, and I agree that doing it as middleware is less hackish.
<br><br>I'll need to play around with it a bit though, because right now the double lambdas around app_fn are over my head. Should the middleware be added to wsgi_intercept so that other potential users can use it?<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Then we could have twill_wsgi functions, e.g.<br><br>--<br>val = twill_wsgi.print_environ('foo_name', 'env_variable_to_print')
<br>--<br><br>or twill script,<br><br>>> extend_with twill_wsgi<br>>> print_environ foo_name env_variable_to_print<br><br>thoughts?<br><font color="#888888"></font></blockquote><div><br>Yeah, that looks solid. I'll play around with it this weekend and see what I can come up with.
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888">--titus<br></font></blockquote></div><br>Thanks for the reply!
<br>-Ken<br><br>