Hey folks, While people are throwing around 1.3 ideas... I think we should start the process of deprecating and removing support for mod_python. Why?
* mod_wsgi is better in every way. * mod_python hasn't had a release since 2007, or a commit since 2008; it's a dead end. The Apache Foundation board voted this month to retire it to the "Attic" - effectively beginning to wind it up. http://attic.apache.org/projects/quetzalcoatl.html * if people are still using it in production in 2012, it is easy to maintain an external handler. I'm proposing the following very predictable timeline: Django 1.3 Use of the modpython handler raises a PendingDeprecationWarning. Update the docs to discourage people from using it. Django 1.4 Use of the modpython handler raises a DeprecationWarning. Django 1.5 Remove the modpython handler from Django (and put it on bitbucket/github?) If someone magically steps up and brings it back to life, we can always halt/reverse the process. Objections? Rob :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
