From 7af62f48e33c5e392b6978607e312f4e033f1de4 Mon Sep 17 00:00:00 2001
From: Jacob Kaplan-Moss <jacob@jacobian.org>
Date: Thu, 21 Jul 2005 17:37:36 +0000
Subject: [PATCH] Added note about using different settings modules in the same
 virtual host (thanks steadicat).

git-svn-id: http://code.djangoproject.com/svn/django/trunk@277 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/modpython.txt | 23 +++++++++++++++++++----
 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/docs/modpython.txt b/docs/modpython.txt
index dc5364a4db..38e6d91165 100644
--- a/docs/modpython.txt
+++ b/docs/modpython.txt
@@ -83,10 +83,25 @@ instance. Just use ``VirtualHost`` for that, like so::
         SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
     </VirtualHost>
 
-Don't put two Django installations within the same ``VirtualHost``. Due to the
-way mod_python caches code in memory, your two Django installations will
-conflict. If you can think of a way to solve this problem, please file a ticket
-in our ticket system.
+If you need to put two Django installations within the same ``VirtualHost``,
+you'll see problems due to the way mod_python caches code in memory.  To fix
+this problem, you'll need to use the ``PythonInterpreter`` directive to give
+different ``<Location>``s seperate interpreters::
+
+    <VirtualHost *>
+        ServerName www.example.com
+        # ...
+        <Location "/something">
+            SetEnv DJANGO_SETTINGS_MODULE myproject.settings.main
+            PythonInterpreter myproject_main
+        </Location>
+        
+        <Location "/admin">
+            SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
+            PythonInterpreter myproject_admin
+        </Location>
+    </VirtualHost>
+
 
 Running a development server with mod_python
 ============================================