On Tue, Sep 07, 2004 at 05:41:17PM -0700, Richard Johannesson wrote:
> Thanks everyone - seems like I should just stick to CGI during testing
> or till got more experience doing web dev using python.

It works well for me, given that my production target is fastCGI, which
is a pretty simple switch (SCGI should be simlarly straightforward, I
believe).  mod_python is the odd one: neither as simple as CGI's "one
request: one process" nor the simply persistent server of fast/S.  I
guess it must be just the ticket for some things, but for me it was
just too much trouble.  It also had a much higher cost if I wanted to
use a different Python release - with *CGI any working version that has
the needed modules can be used just by changing the shebang line; with
mod_python the interpreter is embedded in the binary module.

Right, that's the sort of thing I'd meant to make a start at the other
day when I went and got all imbroglioed mucking with the wiki: notes
toward a comparison of the nine and ninety ways, their pros, cons, and
eccentricities & etc.  Of course I couldn't do more than a start at it
as I haven't experience with all the ways of running Quixote under
Apache, even.

--
One discharges fancy homunculi from one's scheme
by organizing armies of idiots to do the work.  -- Dennett