FYI because there was some wildcarding going on, I think my ServerNames were actually duplicate in the two VirtualHost definitions (unqualified main domain name) and I was accomplishing any differentiation using ServerAlias. According to the mod_python docs < http://www.modpython.org/live/current/doc-html/pyapi-interps.html>, this must have caused my instances to share an interpreter, probably resulting in some unfortunate collisions on key modules (like the settings file, which had the same path in both handlers). So I added the PythonInterpreter directive as suggested by mod_python and as indicated in the Django docs < http://docs.djangoproject.com/en/dev/howto/deployment/modpython/>. Haven't had much opportunity to test, but I expect this will do the trick.
Just wanted to close the loop here on the list in case someone stumbles across this in the future, -- Scott On Wed, Sep 24, 2008 at 12:11 PM, David Durham, Jr. < [EMAIL PROTECTED]> wrote: > > > I see on this thread > > < > http://groups.google.com/group/django-users/browse_thread/thread/4f0cb183eb5b43cd/7be0fa3681b73220?lnk=raot > > > > from last year that there is suspicion that Apache can at times misdirect > > mod_python requests to the wrong mod_python instance. > > You could try mod_wsgi. > > -Dave > > > > -- http://scott.andstuff.org/ | http://truthadorned.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
