I figure anyone using 1.3/2.0 is probably likely to keep using 1.3/2.0 for a long time - backporting security fixes from 2.2 specifically for the UID/resource allocation. I've not attempted mod_wsgi on any of our 1.3 servers nor do I plan to.
What I've planned is a method to deploy 2.2/mod_wsgi and a modified mpm-peruser to work with our unique situation. However, we have been maintaining recipes for deployment -- django being the de facto standard even though I personally use Pylons. Our current system makes it somewhat easy to develop a new deployment script. It would be nice if the different projects included a working default, but, their argument is going to be that it would take too much to create a standard deployment script and maintain it for compatibility across all of the platforms and variations. The number of systems developed every day and the lack of a large installed base means it's always a struggle to automate the middleware. As for your lack of time/state of mind, take a break, find a new hobby, rediscover an old hobby, or something. Remember what you're working for -- or something like that. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
