views:

490

answers:

2

I've been playing with mod_python in apache2 which seems to work differently than python does in general - there's a bit different syntax and things you need to do. It's not very well documented and after a few days of playing with it, I'm really not seeing the point of mod_python at all, especially when things like php are so well documented and available.

I can see how Python works well for system programming, but can anyone give any information as to why I shouldn't just dump python for a web-based application?

+2  A: 

mod_python wasn't really made for doing basic webprogramming. I suggest you go with a framework:

My suggestion is to give python some time. It's easy to get simplicity and lack of power confused. :)

Jason Baker
+14  A: 
  1. Don't use mod_python. A common mistake is take mod_python as "mod_php, but for python" and that is not true. Use mod_wsgi instead.
  2. Choose a web framework. CherryPy. Pylons. Django.
  3. Look at wsgi.org
nosklo
"Use mod_wsgi instead" Seconded! Or SCGI if you find it easier not to be running in the same process.
ephemient
You can run mod_wsgi in a separate process as well. Try reading about "mod_wsgi daemon mode."
Jason Baker
mod_wsgi's daemon mode is *not* available under Windows, though.
Matthew Trevor