I have branched the trunk of mod_wsgi subversion repository to create: http://modwsgi.googlecode.com/svn/branches/mod_wsgi-3.X
If you are tracking subversion yet still want stable code, then follow this branch now instead of trunk. The version string in mod_wsgi trunk is now set as 4.0-TRUNK. Be aware that there is a high probability that a version 4.0 of mod_wsgi will be released in the near future. The reason for releasing mod_wsgi 4.0 so quickly will be to revert the wsgi.version tuple in WSGI environment back to the value (1, 0) from the value (1, 1) it was set to in mod_wsgi 3.0. The existing 3.X branch will be marked as deprecated and everyone would be advised to stop using it to get rid of it. There would be no patch updates made to 3.X branch. Reverting the value of wsgi.version back to be inline with what WSGI PEP 333 specification says it should be is because want to step back from trying to force an update to WSGI specification with a new version number. I just don't see that as a realistic goal anymore and I certainly don't have the energy or time to push that barrow these days anyway. Even if some were to agree to a WSGI 1.1, it is highly unlikely that all WSGI server/adapter providers, plus wsgiref in Python would ever be updated. The confusion it is going to cause and the uncertainties as to whether a WSGI component is designed to only work with either WSGI 1.1, is just not going to be worth the trouble. The best one can probably ever hope for at this time is an amendment to WSGI 1.0 which installs requirement, by way of existing practice, that readline() MUST take an optional argument and also how WSGI should be implemented to Python 3.X as per how it is being done in wsgiref in Python 3.1. Note that doing this will not affect your applications one bit as all the features that mod_wsgi supports will still be exactly as they were before, only the value of wsgi.version will change. You would just continue to use features as you did before, in full knowledge that using parts of the interface or features outside of what WSGI 1.0 defines may mean your code is not portable to other WSGI hosting mechanisms. 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.
