On Tue, Sep 13, 2011 at 8:52 AM, Ruslan <[email protected]> wrote: > I'm trying to start apache + mod_wsgi and I have strong restriction to > put source .py files onto server, so I compile them first and put .pyo > files onto server.
You will have to at least provide the source to the wsgi script file. For instance, the WSGIScriptAlias would have to be home.py, not home.pyo. The extension in this case does not change the behavior of mod_wsgi, in fact, most examples I have seen using the .wsgi extension for the WSGIScriptAlias file (home.wsgi) even though it contains python code. You can then import the rest of your code from the bootstrap, and only provide the .pyc/pyo files for the imported modules. So, if the code you wish to hide is in the wsgi script (home.py) move it elsewhere and import it. -- 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.
