How to use modpython in django version 1.5

40 views
Skip to first unread message

nobody

unread,
Nov 25, 2013, 12:39:48 AM11/25/13
to django...@googlegroups.com
Hi,

After version 1.5, django has disabled mod_python. Can we still use the modpython instead of mod_wsgi? If so, how can we install the mod_python, doesn't seem a package is available in Debian squeeze or wheezy.

Thank you.


Russell Keith-Magee

unread,
Nov 25, 2013, 1:01:35 AM11/25/13
to Django Users
On Mon, Nov 25, 2013 at 1:39 PM, nobody <jupit...@gmail.com> wrote:
Hi,

After version 1.5, django has disabled mod_python. Can we still use the modpython instead of mod_wsgi? If so, how can we install the mod_python, doesn't seem a package is available in Debian squeeze or wheezy.

No, you can't. The reason Django removed support for mod_python is because mod_python is an unmaintained project - and that's coming direct from the maintainers of mod_python. That means it isn't getting bug fixes, nobody is looking after security issues, or memory leaks, or fixing any of the myriad problems that mod_python had (including, but not limited to, a lack of support for Python 3). 

This isn't a recent change, either. The Apache project moved mod_python into the "attic" on 16 Jun 2010. That's 3.5 years ago.

Seriously - there's no reason to be using mod_python these days. You should be using a container based on WSGI -- mod_wsgi if you want to stick with Apache, or any of the other excellent WSGI containers (e.g., gunicorn).

Yours,
Russ Magee %-)



Daniel Roseman

unread,
Nov 25, 2013, 5:17:45 AM11/25/13
to django...@googlegroups.com
No longer quite true. The original developer of mod_python, grisha, has restarted work on it: see http://grisha.org/blog/2013/10/25/mod-python-the-long-story/
However as he explains in that post, he doesn't really see it as a means of running websites, but rather as a Python interface to Apache. So you're still right that mod_wsgi remains the best bet.
--
DR.
Reply all
Reply to author
Forward
0 new messages