[mod_python] installation problem: --prefix is ignored for Python libraries ?

You would have to modify generated dist/Makefile and add extra
arguments when 'python setup.py install' is being done. The
configure/makefile structure of mod_python doesn't allow prefix to be
defined so as to install in alternate location.

Graham

On 23/10/2007, Alec Matusis <matusis at yahoo.com> wrote:
> We are using encap system in our production server, and I am trying to
> upgrade to 3.3.1
>
> I want to install Python libraries not in site-packages, but in
> /usr/local/encap/mod_python-3.3.1
> and then run encap, which would link them into site-packages.
> So I configure:
>
> web10:/path/sys/src/mod_python-3.3.1 # ./configure
> --prefix=/usr/local/encap/mod_python-3.3.1
> --with-apxs=/usr/local/encap/httpd-2.2.6/bin/apxs
> --with-python=/usr/local/bin/python --with-max-locks=64
> #make
> #make install
> And it directly installs instead into
> /usr/local/encap/Python-2.4.1/lib/python2.4/site-packages, ignoring my
> configuration prefix:
> "
> .....
> creating
> /usr/local/encap/Python-2.4.1/lib/python2.4/site-packages/mod_python
> copying build/lib.linux-x86_64-2.4/mod_python/Cookie.py ->
> /usr/local/encap/Python-2.4.1/lib/python2.4/site-packages/mod_python
> .....
> "
>
> How can I force it to install into /usr/local/encap/mod_python-3.3.1 and not
> into site-packages?
>
> Thanks.
>
>
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python
>