On May 16, 12:21 am, "Norman Harman" <[EMAIL PROTECTED]> wrote: > Alex Morega wrote: > > On May 15, 2008, at 02:24 , David Zhou wrote: > >> Are you restarting the server between module changes? > > > By default Django does no caching of responses. It's probably what > > Viktor says: the server (mod_python,mod_wsgi, whatever) won't > > automatically reload the python code if you change it. The automatic > > reload behaviour only happens with Django's built-in development server. > > Not strictly true. With mod_python there's a directive to control > whether apache automatically reloads python code. You *don't* want to > set this on for production code(large performance penalty). > > PythonAutoReload On > > I'm guessingmod_wsgiand others have something similar.
That option for mod_python does absolutely nothing for Django. This is because Django and your application modules for it don't fall into the category of modules thats are candidates for reloading. In mod_wsgi, when using daemon mode, the default behaviour in mod_wsgi 2.0 is a process reloading feature. This is only triggered though when the WSGI script file acting as entry point is changed, and again not arbitrary code. Thus, what you would do is make all your code changes then touch the WSGI script file (ie., update modification time using 'touch' command) and the application will be reloaded on next request. See: http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode Graham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
