Apache mod_python

[Dan]

I've been writing a server application in Python. The app listens on
a socket and interfaces to a database.

Now I'd like to write a web application to also access the database.
It seems natural to use Python. I've installed mod_python (Debian
libapache2-mod-python2.3, mod_python 3.1.3-4).

My question is, how mature/stable is mod_python? Is it suitable for a
production environment? The documentation is a bit lacking, and I've
found some errors in the demo example where it looks like the link
should work, but it doesn't. (Could well be something I'm doing.).
I've also noted that there's still work being done on it.

Thanks.

Dan

[David Fraser]

Dan wrote:

I've been writing a server application in Python. The app listens on
a socket and interfaces to a database.

Now I'd like to write a web application to also access the database.
It seems natural to use Python. I've installed mod_python (Debian
libapache2-mod-python2.3, mod_python 3.1.3-4).

My question is, how mature/stable is mod_python? Is it suitable for a
production environment? The documentation is a bit lacking, and I've
found some errors in the demo example where it looks like the link
should work, but it doesn't. (Could well be something I'm doing.).
I've also noted that there's still work being done on it.

Hi Dan

mod_python is quite mature and stable and usable in a production
environment. However it is fairly low level and a lot of people like to
add another framework on top of it.
If you point out the documentation problems you're having then people
can say whether you're making a mistake or there is really an error

David

[Sizer]

Dan <da*@dontspamme causeidontlikit .com> wrote in
news:np******** *************** *********@4ax.c om:

My question is, how mature/stable is mod_python? Is it suitable for a
production environment? The documentation is a bit lacking, and I've

I use mod_python for all my web stuff, including several live production
sites - no problems so far. Admittedly, I don't use anything too
complicated - usually just the handler and publisher syntax and a little
bit of authentication. Plus MySQL on the back end.

From what I've been told, the one gotcha is that you want to make sure that
different on-server users aren't sharing the same copy of mod_python, since
they'll have a shared context. Which would only a problem where you're
running a server open for lots of people to set up their own pages. I own
all the servers being used so it's not an issue.