On Feb 25, 9:53 pm, Aljosa Mohorovic <[EMAIL PROTECTED]> wrote: > django is not in system/pythonpath but is in '/var/sites/test' path > which i define in PythonPath when i configure site/django project. > > is it possible not to have django in system wide path but to define in > apache conf via PythonPath where to find django? > > apache conf below is example of a way that i would like to try to > control django version but what happens if another site uses django? > what kind of conflicts can i expect? > > please post any ideas, tips, tricks, problems, theory, anything > related to configuringmod_pythonfor django apps. > > <Location "/site_app_1"> > SetHandler python-program > PythonHandler django.core.handlers.modpython > SetEnv DJANGO_SETTINGS_MODULE site_app_1.settings > PythonDebug On > PythonPath "['/var/sites/test'] + sys.path" > </Location> > > <Location "/site_app_2"> > SetHandler python-program > PythonHandler django.core.handlers.modpython > SetEnv DJANGO_SETTINGS_MODULE site_app_2.settings > PythonDebug On > PythonPath "['/var/sites/test'] + sys.path" > </Location>
This will not work because the default behaviour for mod_python is to only assign one Python interpreter instance for a whole VirtualHost. You need to use PythonInterpreter directive for each location and designate distinct names for interpreter to be used, otherwise the applications will clash. BTW, do you control all Django instances or are they developed by different users? Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
