On 14 April 2012 05:34, Bill Freeman <[email protected]> wrote: > On 4/12/12, Graham Dumpleton <[email protected]> wrote: >> 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 >> > Neither the company I work for nor I have used mod_python in a long > while. If I recall correctly, it has been notated as unsupported for > a long time. > > Is there really anything you can do with mod_python that you can't do > with mod_wsgi?
Yes, various things. > Sure, there may be folks with an ancient mod_python application that > they don't want to modify, but surely that is the correct circumstance > in which to force people to run multiple apache instances, rather than > for those running a bunch of apps all using mod_wsgi, all over the > same base python. > > Minor releases are often not fully backward compatible. For instance, > if you have an app that uses (a library that uses) "as" as a variable > name, then moving from python 2.6 to python 2.7 broke it. Still, I > can see how becoming unable to be loaded at the same time as > mod_python seems like a more significant change. I, too, am less > comfortable with that for a minor release, particularly if you haven't > gone a round or two with a deprecation warning. Python has a X.Y.Z version numbering scheme. In mod_wsgi it is only X.Y. The general approach with mod_wsgi is therefore only to break on new X and not Y. > But, particularly since there is the workaround of running two > apaches, I think that the benefit outweighs the cost. As it turns out I had already back ported Python 3.2 support into 3.X branch ages ago. I didn't prevent mod_python from working explicitly, but seems I don't guarantee it will work either. One last fiddle is still in the code for when Python 2.X is used but I haven't actually bothered to see if mod_python and the modified mod_wsgi still works together. Either way, I still need to go see if mod_wsgi will even work for Python 3.3 as I haven't done that yet. Graham > Bill > > -- > 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. > -- 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.
