There are a number of shared hosting companies that are still on 1.3/2.0 for SetUID. Whether they support mod_wsgi currently is a question. Whether they will be able to support it in the future might be an issue.
I know at one point you and I discussed what it would take to get broader acceptance of mod_wsgi in hosting environments. As long as there is a viable path for mod_wsgi support somewhere that supports 1.3/2.0, you should be ok. Splitting development into a legacy/new branch would cause some extra work, but, as long as the basic functionality is there for 1.3/2.0, and security fixes are backported, I would imagine the workload to be fairly light. We do still have a handful of apache 1.3 machines, no apache 2.0 machines and the rest running apache 2.2. However, the number of people utilizing mod_wsgi is a pretty small number for us. -- 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.
