mod_python and unique PythonInterpreters
|Reported by:||lifewithryan||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The documentation for PythonInterpreter when using mod_python appears to be mis-stated. The experience I had was running 2 django instances but in two different virtual hosts. The docs state you need to add a python intrepreter if you are running two django instances in the same virtual host. However, by not having a PythonInterpreter setup the python cache still appeared to be getting messed up. As soon as I added the PythonInterpreter, things started working as expected.
The text in question is: "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:"
Again, as stated above, the docs lead you to believe that if you are running two django instances in different virtual hosts, you don't need this. Perhaps I'm wrong and something else was at play, but to me, this did the trick.
Change History (4)
comment:1 Changed 7 years ago by grahamd
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
comment:3 Changed 7 years ago by mtredinnick
- Resolution set to fixed
- Status changed from new to closed