Does Apache have mod_wsgi? If so, you can get them to make a change to your .conf file as detailed at http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode
This means you only need to 'touch' the .wsgi file specified by the WSGIScriptAlias to get your Apache process to restart. Works a treat! I moved away from mod_python for the very reason you've outlined. The wealth of information on mod_wsgi is immense! Cheers, Tone On Aug 28, 6:25 pm, Gremmie <[EMAIL PROTECTED]> wrote: > On Aug 27, 8:18 pm, Richard Simões <[EMAIL PROTECTED]> wrote:> I have > non-root access to a server with apache2 and mod_python. I > > installed django with svn to a location in my home directory and > > created a test project. When I go to a URL defined with urls.py and > > views.py, 9/10 times the expected page is shown. The remaining 1/10 > > times the "It worked!" page pops up. Searching for this problem seems > > a bit difficult. Any idea on what could be happening? > > It sounds like some of the apache processes are running your new code, > but some of the other processes are still running the typical > mod_python test program you use to see if mod_python is configured > correctly. You will need to restart apache after every code change. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
