Enhance Mod Python documentation regarding multiple Trac instances in a single virtualhost

[gergely.kis@…]

If you use multiple Trac instances (e.g. different trac versions) in a single virtualhost, then you will need to add a

PythonInterpreter  myproject_python

directive into the Location section. For example:

<Location /projects/myproject1>
   SetHandler mod_python
   PythonHandler trac.web.modpython_frontend 
   PythonOption TracEnv /var/trac/myproject
   PythonOption TracUriRoot /projects/myproject
   PythonPath "sys.path + ['/path/to/trac-version1/lib/python2.3/site-packages']"
   PythonInterpreter myproject1_python
</Location>

<Location /projects/myproject2>
   SetHandler mod_python
   PythonHandler trac.web.modpython_frontend 
   PythonOption TracEnv /var/trac/myproject
   PythonOption TracUriRoot /projects/myproject
   PythonPath "sys.path + ['/path/to/trac-version2/lib/python2.3/site-packages']"
   PythonInterpreter myproject2_python
</Location>

The value of PythonInterpreter? does not matter as long as it is unique in a virtual host.

The idea was taken from the Django documentation: http://www.djangoproject.com/documentation/modpython/

[cboos]

Caveat: using different "PythonInterpreter" may introduce issues, like trigerring segfaults in the Subversion python bindings. See #3455.

[cboos]

As using different Python interpreters is not recommended when using Subversion and might be problematic for other C extensions, we shouldn't advise to use that setup, quite the opposite.

Those caveats should be more clearly exposed in the TracModPython page though.

[osimons]

Replying to cboos:

Those caveats should be more clearly exposed in the TracModPython page though.

Isn't the current wiki:TracModPython#Subversionissues (and the page as a whole) a balanced treatment of the issue for this ticket? Close?

[cboos]

Right, it looks like the PythonInterpreter main_interpreter directive is now written all over the place there ;-)