> FWIW, all the speculation in that discussion was based on me having to > interpret second hand information sent to me by others. Usually those > people didn't know what to look for and could well not have been doing > the correct thing or interpreting the result properly. Part of the > feedback could also have been based on older versions of Python which > possibly may not have worked in exactly the same way for all I know. > > It is only recently that I have started building mod_wsgi myself onWindowsand > even then I don't really test it onWindowsmuch. Now that > I have the environment, I am in a position to properly research this > issue however, so I will create a ticket to do that. I am not sure > though whether changes will be made for mod_wsgi 3.0 however, depends > on how much time I have.
Thank you for your attention to this. As an interim solution, you might consider adding a preprocessor symbol that will enable WSGIPythonHome on Windows (currently it's unconditionally disabled on Windows). > PS. I have sent this back onto list with bcc to you in case you don't > want your details public given you sent me this direct. And thank you for your concern for my privacy, but I had actually intended that message for the list; it was sent directly to you because I generally have no idea what I'm doing with Google Groups. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
