Wiley, I ran into the same problem. Even though I wasn't running two
Django installations in the same VirtualHost caching seemed to be
crossing my installations together. Adding the PythonInterpreter
directive to the virtual hosts did the trick for me - you won't need
the Location directive, just PythonInterpreter. See the following from
the "Django with mod python" documentation.
Bob
"If you need to put two Django installations within the same
VirtualHost, you'll need to take a special precaution to ensure
mod_python's cache doesn't mess things up. Use the PythonInterpreter
directive to give different <Location> directives separate
interpreters:"
<VirtualHost *>
ServerName www.example.com
# ...
<Location "/something">
SetEnv DJANGO_SETTINGS_MODULE mysite.settings
PythonInterpreter mysite
</Location>
<Location "/otherthing">
SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings
PythonInterpreter mysite_other
</Location>
</VirtualHost>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
