p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed spelling error and reworded mod_python PythonInterpreter section of docs 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@285 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2005-07-21 19:42:51 +00:00
parent 8b58f8b3ae
commit f8e5df6d7e
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/modpython.txt
View File

@ -83,10 +83,10 @@ instance. Just use ``VirtualHost`` for that, like so::
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
</VirtualHost>
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>`` directives seperate interpreters::
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
@ -102,6 +102,8 @@ different ``<Location>`` directives seperate interpreters::
</Location>
</VirtualHost>
The values of ``PythonInterpreter`` don't really matter, as long as they're
different between the two ``Location`` blocks.
Running a development server with mod_python
============================================