|
Joost Yervante Damad
joost.damad at siemens.atea.be
Tue Mar 20 08:06:31 EST 2001
'Ensim-Newsgroups.Mailing-Lists.Mod_Python-List' wrote about '[mod_python] setup of python2.1 with and without mod_python' - Mon, Mar 19, 2001 at 11:10:18PM CET
> i want to be able to run regular python via shell and python via mod_python.
>
> i got modpython to compile under 2.1beta with threading off.
>
> is it possible to have the following environment on a server:
>
> /usr/lib/python2.1/* compiled with threading on (pyc + so files)
> /usr/bin/python compiled with threading on
> ** and **
> apache's mod_python.so : dso apache module compiled with python threading
> off (i downloaded 2.1 source, did a configure --without-threads, and
> compiled mod_python against this source tree)
>
> if my mod_python scripts import libraries from /usr/lib/python2.1/ (ie
> import pyc and so files compiled with --with-threads), will it break in the
> above environment?
>
> basically, i don't want to have 2 different /usr/lib/python2.1...one for
> regular python (invoked via shell) and one for use with mod_python.
>
Good point. In our lab setup we do the same:
* mod_python uses an embedded non-threaded python interpreted
* /opt/Python/* contains an installed normal python which is
compiled *with* threading.
If I now use modules from that python it seems to work fine.
Is this legal/okay ?
--
Joost Damad - Siemens IC D NC A - +3214252297
--
Five is a sufficiently close approximation to infinity.
-- Robert Firth
"One, two, five."
-- Monty Python and the Holy Grail
|