Hello, everyone. I'd like Django's WSGI support to be as good as in the other WSGI frameworks (or better).
With this in mind, I have developed a project called twod.wsgi [1] which brings full WSGI capabilities to Django, whether running in development or deployment. This project is fully tested, 100% backwards compatible and has now been in use for over 5 months in a production environment. Ideally I think full WSGI support is something that should be available out-of-the-box in Django and therefore I want to contribute it to Django. (And I'm reopening this discussion, as suggested when I tried to push it to Django 1.2 [2].) Among many other things, one of the components alone provides solutions to some enterprise requirements for Django <http://groups.google.com/group/django-developers/browse_thread/thread/c89e028a536514d3>: * It’s now possible to run code at startup time, in a straight-forward yet extremely flexible fashion, which will also work on development servers if you want it to – not only when deployed on a production server. * You can now stop using a Python module to store your application settings, in order to use an intuitive and widely used mechanism that scales up and scales down. It will just work and you won’t have to update any other file in your application. * By providing full WSGI support in development mode, we are able to work around the differences in the process environment between django development server and django hosted using mod_wsgi <http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html> * It’s finally possible to run WSGI middleware in development servers, the same way you may do it on production servers. And this is just the tip of the iceberg. By improving Django’s interoperability, we would gain the ability to rapidly integrate many pieces of third party software with Django, or simply use a component which outperforms Django’s current implementation for your requirements. If you want to read more about how we’ve done this, you can look here: http://packages.python.org/twod.wsgi/manual/index.html#introduction We're willing to work closely with the core development team to adapt twod.wsgi if necessary and integrate it in Django 1.3. What do you think? - Gustavo Narea. [1] http://packages.python.org/twod.wsgi/ [2] http://groups.google.com/group/django-developers/browse_thread/thread/08c7ffeee7b9343c -- 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.
