On 24/10/2014, at 8:32 AM, ystrickler <[email protected]> wrote: > I am trying to run a server deployed from an egg, and it requires -O to run > properly (if __debug__ is true, it will look for resources in files that > aren't part of the egg). On one server, this works fine, but on the other, it > appears that __debug__ is true regardless of what I set WSGIPythonOptimize > to. I am not loading mod_python. Is there anything else that could interfere > with the directive?
Is that package one which is publicly available? A package which is dependent on what the Python optimise flag (__debug__) is set to, and in particular requiring that code run as -O when using an installed version of the package, has arguably made a poor decision. This is because although there is a -O and -OO options, no one ever really uses them much in practice from what I have seen. One also can't even use -OO in lots of third party modules as it removes doc strings which can then break various code that cannot deal with __doc__ being None rather than a string. The -O option generally doesn't do much more than provide alternate byte code cache files which aren't of much benefit in long running processes such as mod_wsgi as everything is only loaded at startup anyway. Anyway, that said, what is the actual mod_wsgi configuration snippets you have in your Apache configuration file and what version of Python and mod_wsgi are you using? I can think of no reason off hand why there would be a problem with WSGIPythonOptimize with the exception that it will not work if mod_python were being loaded at the same time. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
