On Sun, Feb 26, 2006 at 09:53:59AM -0500, David Higgs wrote: > I managed to run mod_python several years ago and was pulling my hair > out for the better part of a week until I got it working. I never got > the dynamic module to work, but was successful in building it into > apache statically. Additionally, mod_python requires a separate > python installation without thread support. Apache's chroot might > cause you further difficulty...
These days, you're better off running a standalone python appserver exposing http or scgi [http://www.mems-exchange.org/software/scgi/] and pointing apache at it with mod_proxy or mod_scgi. There's flup [http://www.saddi.com/software/flup/], which gives you a nice threading WSGI engine, and then you can either write your code as a WSGI server or plug in one of the frameworks like web.py, django, whatever, they all serve WSGI. Mod_python, even when it works, is a pretty big memory hog because every apache handler has its own python interpreter.
