On 28 April 2012 02:16, poiuytrez2 <[email protected]> wrote: > Hello, > > I am developping a software for Windows which embed a python (2.7) web > application running with mod_wsgi (3.3). > Until now, I have adding the path to the python executable in the windows > PATH. > > Some of my users have already an old python environment (2.5) which is used > by an other software (collabsvn server). > > I would like that both software run side by side. Both software have their > own apache instance. > > I tried to use the WSGIPythonHome for my software and I did not succeed (I > have read that it is not compatible for Windows). > Is there a workaround for Windows to avoid to set the python executable in > the windows PATH ?
If the Python installations were all installed for all users, and not just the specific user it was installed as, I don't believe you should have this issue. Certainly not if they are different Python versions. The only issue might be when a third party application has its own Python version which conflicts with a system wide one that mod_wsgi was using. In that case, need to ensure the PATH for Apache has the system wide one before any other so correct DLL for Python is found. 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.
