> > > Anyway, that is where I am currently stuck, not knowing what really to > do. Ditching Apache 1.3 support was to allow me the option of cleaning > up the existing mod_wsgi code to make it easier to maintain and add > new features where I can. Based on how that goes then can make a > decision as to what to do. > > Hi Graham,
Python took a bold move to break backward compatibility with 3.x. And you were (and still are) one of the first/only ones to support it. Hanging on to apache 1.3 will reduce the effectiveness of your time on the project, and therefore the project's effectiveness itself. Take the step forward. The world surely is not going in the direction of Apache 1.3. As another poster pointed out - virtually all modern distributions ship with Apache 2.2. You will not regret it, nor will 98% of your users. The other 2% need to bear the burden of upgrading apache, rather than you bear the burden of them not upgrading apache. Thanks for everything, Jason Garber -- 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.
