I found this message by Graham Dumpleton where he explains the problem: http://www.modpython.org/pipermail/mod_python/2006-January/020079.html
I belive this is the explanation: > When you see what you expect, it is because the request was handled by a > different Apache child process which had never previously loaded your > code. Since it is the first time it has needed to load it, it will > obviously get the most recent version. > When you don't see what you expect, it is because the request was > handled by the the existing Apache child process which had already > loaded the code. According to that post this should be fixed in mod_python 3.2.6 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
