mod_wsgi, mod_python, or just cgi?

Question

I\'ve been playing around with my own webserver (Apache+Ubuntu) and python. From what I\'ve seen there are 3(?) main ways of doing this:

1. Apache configured to handl

Answer 1

I would go with mod_wsgi too.

If you want a deeper understanding about the question, have a look at this:

• Apache, FastCGI and Python, by Ferry Boender

Good stuff!

Answer 2

mod_python is dead, so using mod_python probably isn't a good idea for new projects. Personally, I prefer to use mod_wsgi over CGI (or FastCGI). It's dead-simple to set up, and much more efficient.

Answer 3

1. Don't use CGI. It's inefficient. Spawning a new process for each request. No thanks

2. Dont't spend much time with mod_python

3. Use mod_wsgi.

If you want to write CGI-like stuff without a framework, use mod_wsgi anyway. The WSGI standard (PEP 333) is essential for creating web applications in an easy, interchangeable, reusable, plug-and-playable way.

Answer 4

Mod_Python

mod_python is alive and well. See here: http://modpython.org/. Furthermore, here's the documentation for the latest release, 3.5.0, with support for Python 3: http://modpython.org/live/current/modpython.pdf. Currently I use it.

Mod_WSGI

mod_wsgi thinks of itself as not to be used barebones, but with a framework, such as Flask.