On Sat, Aug 28, 2010 at 7:27 AM, Jesse <adles...@gmail.com> wrote:
> Do I not need it to run Apache on Windows with Django?  Or what is the
> alternative?  This is the 5th server I've set up and I've always used
> mod_python until now.  How do I get past this mod_python step?

Seriously - the answer is to stop using mod_python. The Apache project
has officially deprecated mod_python [1]. The last release was in
2008, and by deprecating the project, Apache has signalled that there
aren't going to be any releases or updates in the future. Django will
begin the deprecation process for the mod_python backend in the 1.3
cycle [2], so when Django 1.5 comes out, there won't be any support
for mod_python.

At this point in time, if you're investing time and effort setting up
mod_python servers, you're wasting time and effort. You have about
18-24 months to move away from mod_python before your Django projects
stop working.

WSGI is very much the way forward; mod_wsgi is available for Apache,
and a number of other web servers; several of these web servers
(including Apache) are available on Windows. There are also FastCGI
deployment options available. I can't comment on the best option for
Windows deployment, though.

[1] http://attic.apache.org/projects/quetzalcoatl.html
[2] http://code.djangoproject.com/ticket/13820

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to