Sunday, November 24, 2013

Re: How to use modpython in django version 1.5


On Mon, Nov 25, 2013 at 1:39 PM, nobody <jupiter.hce@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 %-)



--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAJxq8485qfPrn336VV-LhGjc4UnSZ4kKHSR38rii3n%3DpHi7qbg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment