On 2007-03-06 20:51:14 -0700, "leland" <[EMAIL PROTECTED]> said:
> > joe - thanks for the tip. turns out it wasn't including the > vhosts.conf file. so i got everything to work on mediatemple's (dv) > 3.0 server. now, i've run into another issue. my company runs a (dv) > 2.0 box that came standard with python 2.2. i upgraded to python 2.3, > but now mod_python still points to the old python 2.2 install. does > anyone know how to change which python mod_python points to? or do i > have to re-compile? i thought maybe there would be a config file or > something like that for mod_python that would allow me to change this > easily. any help would be greatly appreciated! > > thanks > > > You will have to build mod_python with python 2.3. it is pretty simple. just download mod_python and point it to the apache you are running (which should automatically be detected) and python 2.3 (you may have to point it to the python executable if it isn't in the path). then make sure you make a backup of the current mod_python.so just in case something goes wrong. then do a make install and it will put itself where it should go. I believe this is in /etc/httpd/modules which symlinks to /usr/lib/httpd/modules. Restart apache and you should be ready to go. -- Brian Rosner http://www.brosner.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
