> Hi Scott, > you mean to compile py file on fly using this directive? I don't yet know if > it all makes sense.
I was just suggesting that you look at the WSGIImportScript configuration directive if you are concerned about the compilation into Python byte code taking longer than you want when the application is started for the first time. As the directive explains, "the WSGIImportScript can be used to preload a WSGI application script file on process start so that it is ready when actual user requests arrive." I apologize if I am telling you things you already know about Python, but you do not yourself (under most circumstances) need to force Python to compile your Python code into byte code. It will do that when your scripts/modules are loaded by the Python interpreter for the first time. Using py_compile isn't usually necessary unless you expect for some reason that the Python interpreter will not have write permissions to create the .pyc files. > > In contrast, I know that mod_wsgi already has some concerns about > compilation of .py files: > http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIPythonOptimize > > So, I am just trying to understand what is the Right Way to go. > > best regards > -- > Valery A.Khamenya > > > On Tue, Jun 30, 2009 at 2:44 PM, Scott Koranda <[email protected]> wrote: > > > > > Perhaps WSGIImportScript could help you? > > > > > > http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIImportScript > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
