Actually, I use the built-in server (as I am still developing). My guess was the pyc files are not rebuilt, but even when I delete them, I still get the same behaviour.
Just a minute ago, I've tried to switch off browser caching, before I just Ctrl+R-ed the page. This seems to work. :) Thanks for your help, at least I've learned something about mod_python. ;) V On May 15, 4:21 pm, "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 guessing mod_wsgi and others have something similar. > > -- > Norman J. Harman Jr. 512 912-5939 > Technology Solutions Group, Austin American-Statesman > ___________________________________________________________________________ > Get out and about this spring with the Statesman! In print and online, > the Statesman has the area's Best Bets and recreation events. > Pick up your copy today or go to statesman.com 24/7. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
