Re: where does this caching come?

On May 16, 8:44 am, "Norman Harman" <[EMAIL PROTECTED]> wrote: > Graham Dumpleton wrote: > > 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? >

Re: where does this caching come?

Graham Dumpleton wrote: > 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 >>>

Re: where does this caching come?

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

Re: where does this caching come?

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

Re: where does this caching come?

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

Re: where does this caching come?

On May 15, 2008, at 02:24 , David Zhou wrote: > > On May 14, 2008, at 7:06 PM, Viktor Nagy wrote: > >> one of my functions follows, here it doesn't matter if I uncomment >> the >> raide exception line, it never gets raised. On the other hand I am >> sent to the authorization page. The

Re: where does this caching come?

On May 14, 2008, at 7:06 PM, Viktor Nagy wrote: > one of my functions follows, here it doesn't matter if I uncomment the > raide exception line, it never gets raised. On the other hand I am > sent to the authorization page. The getDocument function get's called > from a "request handler"

where does this caching come?

Hello, I am kind of new to django, and trying to build a small app just to learn it (it is an app to interact with Google Calendar and Docs). My problem is, that django seemingly always caches "something". I tried to get rid of this behavior by adding either CACHE_BACKEND = 'dummy:///' or