From 03fcf19fd2043fe096d8ac63abb3fd7e533b639a Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Fri, 24 Oct 2008 09:26:09 +0000 Subject: [PATCH] Fixed #9434 -- Added a note to the mod_python docs regarding requiring PythonInterpreter in different VirtualHost blocks that share the same server name. Thanks to Graham Dumpleton for the clarification. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9268 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/deployment/modpython.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/howto/deployment/modpython.txt b/docs/howto/deployment/modpython.txt index 7612b40020..8799b390fe 100644 --- a/docs/howto/deployment/modpython.txt +++ b/docs/howto/deployment/modpython.txt @@ -160,7 +160,8 @@ instance. Just use ``VirtualHost`` for that, like so:: SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings -If you need to put two Django installations within the same ``VirtualHost``, +If you need to put two Django installations within the same ``VirtualHost`` +(or in different ``VirtualHost`` blocks that share the same server name), 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 ```` directives separate interpreters::