Ah, that does make sense. Yeah I am running with a production server, but using a virtual host to contain out the production site from development. I suppose I can just build another Apache and strip it down for my development needs. Thanks for the tip.
On Jan 26, 11:11 am, "Waylan Limberg" <[EMAIL PROTECTED]> wrote: > On 1/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I am new to Python web development, but not web development in general. > > I have installed mod_python 3.2.10 alongside my currently running > > Apache 2.0.59. All is working fine, but one thing. I am currently > > building a Django application and I have no problems making it. > > However, I'll edit a file to tweak some stuff and upload the changes. > > It seems somewhere in the request the code is getting cached. So I > > have reload the page a couple times before I can get the current code > > on the filesystem. And it will continue to cycle through old revisions > > of the code. Is this a problem with mod_python, python, or django? I > > don't have any caching modules installed for Apache. Any ideas?Are you > > restarting apache after each change? > > If your just using the server for development then you can add > MaxRequestsPerChild 1 to your config file to force Apache to reload > everything for each request. Just don't do that on a production > server. > > -- > ---- > Waylan Limberg > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
