Hi Anton, On Wed, Jun 23, 2010 at 10:13 PM, Anton Bessonov <exe...@googlemail.com> wrote: >> >> * mod_wsgi is better in every way. > > And? Jinja2-Template Engine is every way better as Django Template Engine. > Drop DJango Template Engine and support Jinja2?
Russell explained it, but mod_wsgi: - is actively developed - implements the python web-app standards - has great documentation - supports both Python 2 & 3 - is trying hard to address different hosting models, including shared hosting. mod_python on the other hand: - is abandoned & has no developers - has a LOT of outstanding bugs, many quite serious - will never work with Python 3 without enormous effort - does everything its own special 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 >> > > And? Cobol is old and dead, but see financial and insurance sector. People are actively developing in and with COBOL (eg. the industries you mentioned). The cool kids don't like it - that's different. A new Visual Studio COBOL tool was released just a couple of months ago, as an example. >> >> * if people are still using it in production in 2012, it is easy to >> maintain an external handler. > > External handler is good idea generally for all handlers. And yes, > enterprise are still using it in production in 2199. They'd have to be both: - upgrading Django - upgrading Python (since by Django1.5 you'll need Python2.7 iirc) - not upgrading apache (I'd expect mod_python will break with new apache releases at some point) - not upgrading mod_python > -1. This is'nt arguments to remove support for mod_python. It's produce > sensless work. As Gustavo said in the other thread, removing mod_python will simplify request handling quite a bit, allow Django to be a pure WSGI application (so it can interact better with other Python WSGI apps), and it's less code to maintain - we don't want unused code rotting in the Django codebase. 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.
