> On Fri, Sep 03, 2004 at 04:32:40PM -0700, rtjohan@syspres.com wrote:
> > Just getting started with Quixote + mod_python. Starting by modifying
> > the demo app, but changes are not coming up? So, wondering what's a
> > good test workflow when using Quixote & mod_python for web application?
> > Does apache need to be restarted after changes?

> IMO plain old CGI is da bomb for development.  It services requests
> more slowly, sure, but that's a small price to pay for not having to
> restart the whole bloody server in order to fix a stupid typo.  First
> make it right, then make it fast.  :-)

Check this message:
http://mail.mems-exchange.org/pipermail/quixote-users/2003-August/001908.html


If you want to have mod_python do 'one-shot' serving of your quixote application
during developent (just as with cgi) to ensure that all your changes show up
immediately, without server restarts, all you need to do is edit your
httpd.conf:

MaxRequestsPerChild 1
KeepAlive Off

Of course, that's not acceptable in production; also, it will hide those errors
that arise only upon repeated execution.


I always use this trick while developing: speed is probably comparable to CGIs
but you can keep the same handler and session manager you will use in
production. These details may be not trasparently portable between a CGI and a
mod_python publishing environment.

Occasionally the first request after an update fixing an error fails with a
Publisher complaining there can't be two instances but a further request works
fine: i think it's not a pain.

I keep a #XXX comment next to those lines do quickly find them. A grep, two
comments and an apache restart and your app will run to production speed.

Bye

Daniele