On 13 April 2012 06:06, Bill Freeman <[email protected]> wrote: > On 4/12/12, Krzysztof Jurkiewicz <[email protected]> wrote: >> Hello >> I have django + mod_wsgi + apache2 and virtualhost and it works great. >> I found WSGIPythonHome option but I cant put it in virtualhost but in >> global (quite pointless, because I want different djangos. So how do I >> pull this off to point at multiple pythons (I have on on virtualenv). >> > > If you build a mod_wsgi 4.x from the repository, you will get access to > a new feature, which is the ability to pas a "python-home=" option to > WSGIDaemonProcess. I have used it successfully. There are restrictions, > see Graham's comments in the recent discussion of the feature. Most > significant is that all the virtual environments you are using must be > based on the same root python install.
Because of needing to bring out a mod_wsgi 3.4 with Apache 2.4 support and new directive for hash seen randomisation, the python-home option may well get back ported as well. I still need to look at how much work it will be to also back port Python 3.2+ support. Problem is if I do the latter, it will immediately break installations using mod_python at same time as correct threading API usage which would be applied across Python 2.X code as well, conflicts with the incorrect usage that mod_python does and which mod_wsgi has had hacks in place to work around. The hacks will need to be removed. I am not too keen on breaking concurrent mod_python usage in a minor version update, but it may be time to break mod_python. In mod_wsgi 4.0 it will actually abort Apache startup with error message if you load both mod_python and mod_wsgi at the same time. Comments? 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.
