On Jan 7, 4:13 am, Graham Dumpleton <[email protected]> wrote: > Because of those problems, Interpreter reloading was removed and > proper Process reloading added mod_wsgi 2.X as default instead for > mod_wsgi daemon mode. Thus, touching the WSGI script file now causes > whole daemon process to shutdown and new one created, just as if > Python process itself had been stopped an started. > > Just be aware that some packages, including lxml (because of > simplified GIL state API usage) and some older versions of psycopg2 > (because of a bad coding), have problems running in sub interpreters > and must run in main interpreter in the process. This is a separate > issue to sub interpreter destruction problem. Thus, if using lxml, you > probably still need to delegate application to run in main interpreter > using: > > WSGIApplicationGroup %{GLOBAL}
OK - Let me see if I have this right. If I'm using lxml or any other "problematic" module, and I use WSGIApplicationGroup as described, will I be able to safely have code changes register by simply touching the WSGI script? And if so, what are the downsides to using this method? The end goal is to be able to have code changes implemented without restarting Apache... Thanks, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
