Just a warning. I am refactoring the mod_wsgi.c code file in mod_wsgi source code, splitting it into multiple files and generally cleaning up the code.
As part of this process I am dropping support for Apache 1.3 as well as support for running mod_python in same Apache instance at the same time. The mod_python support is being dropped because changes to use of threading APIs required to make code compatible with Python 3.2 would likely cause a problem with concurrent mod_python support due to fact that mod_python uses the APIs wrongly. In other words, can't use the hacks I used to use to allow mod_python to work at same time and I really don't want to go back and revisit mod_python to work out another way of doing it. I am also looking at dropping support for running mod_wsgi on Apache 2.X build with underlying Apache Runtime Library (APR) which doesn't have thread support enabled. Till now, if such an APR is being used, then daemon mode would simply not be available. Am looking at saying that mod_wsgi simply doesn't support that combination. This would only affect some variants of BSD systems which insist on still shipping an APR with no thread support included. End result of all this is that there is a risk that as I check in changes that I may break something and not notice. I am going to endeavour to start including a whole lot of test WSGI applications in mod_wsgi source code and use them to validate things as I go. What all this clean up will allow me to do is to more easily add new features, something which I will ask for feedback on in a separate mail message. Graham -- 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.
