I still haven't had the time to progress mod_wsgi 4.0, but I did manage to get a good block of time today to back port a lot of stuff from the mod_wsgi 4.0 development version to the mod_wsgi 3.X branch so can release the changes as mod_wsgi 3.4. That leaves just the more experimental stuff in mod_wsgi 4.0.
Normally I would not use a minor version release to put out substantial new features, but mod_wsgi 4.0 is going to drag on for a while yet, so didn't have much choice if wanted to get an updated version out with things like Python 3.2+ and Apache 2.4 support. The cumulative list of all the stuff that will be in mod_wsgi 3.4 can be found at: http://code.google.com/p/modwsgi/wiki/ChangesInVersion0304 Because I back ported the changes quite quickly, it can all do with some good testing and needs to be checked against the main Python and Apache versions still. I will make a release candidate tar ball to make that a bit easier task rather than relying on people having to use Mercurial to get it from the source code repository. Before that though there are still a few new changes I am looking at to integrate. These changes are: 1. Means of turning on hash seed randomisation with recent updates of Python. I still have a few issues to sort out here. I was supplied a patch, but it doesn't go far enough and deal adequately with issues like upgrading patch levels of Python against a mod_wsgi compiled against an older version. It also didn't allow hash seeding, only randomisation. 2. Means in authentication handler defined by WSGIUserScript of overriding the value of REMOTE_USER that is then in turn passed onto the WSGI application. 3. Changes to WSGI environ variable naming restrictions, used when passing through headers to allow % such that can use % encoded header values to pass through with encoded UTF-8. See as discussed in 'http://groups.google.com/group/modwsgi/browse_thread/thread/676b4272221bc1f7/42c8e7e335f249c1'. There have bound to have been a few other features people have requested and although I will try and go back through email and tickets so see any that could be done, if there was something you were waiting on, then speak up now. My next likely chance to do any more work on this will be next weekend so you have till then to give me your wish list items or to give any feedback on the current code if you are able to test it by grabbing it from the source code repo. 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.
