On Dec 19 2008, 5:46�am, "Graham Dumpleton" <[email protected]> wrote: > This just highlights some stuff which was already in documentation, > but tend to find that people don't read deep enough to realise this is > possible and was getting a bit tired of comments onDjangoforums and > irc channels saying mod_wsgi couldn't do this. :-)
Hi, I had a simple question about this: At some point in the past, our group considered using mod_wsgi (for, say, production purposes) with Django, with the intention of not having to restart Apache (on Linux) every time there is a change in the Django code. At the time we didn't pursue it because of issues with using certain modules (e.g. psycopg2, lxml) not behaving when there was a code change. Does this problem still exist when one uses the Process reload mechanism? Our final goal is to have the production site reflect changes after simply touching the wsgi file - and 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 -~----------~----~----~----~------~----~------~--~---
