[mod_python] mod_python calls the wrong python executable

On Wednesday 19 July 2006 09:30, mvanier wrote:
> I'm trying to run mod_python using the latest mod_python snapshot with
> apache 2.2 (compiled from source) on Debian Linux.
> 
> The sys.path of this python interpreter is the one that would exist if
> /usr/bin/python2.4 (which was installed by Debian) was called instead of
> the correct one, which (in my case) is
> /usr/local/packages/python/bin/python (which I compiled and installed
> myself from source).  I specified this executable when I configured
> mod_python (using the --with-python option).  For some reason, though, it
> isn't getting used.  Any ideas would be appreciated.
>
I know this doesn't answer your specific query, but if you're using Debian, 
why not just go

# apt-get install libapache2-mod-python2.4

Cheers,
Richard
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Richard Lewis
Sonic Arts Research Archive
http://www.sara.uea.ac.uk/
JID: ironchicken at jabber.earth.li
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-