|
Gregory (Grisha) Trubetskoy
grisha at modpython.org
Mon Jan 28 13:40:57 EST 2002
If I recall correctly, the issue here is that until Python is installed (i.e. make install was run), there is no way to determine some install time parameters, such as where the lib directory is. the last paragraph on this page talks about it a little bit: http://www.modpython.org/live/mod_python-2.7.6/doc-html/inst-configure.html Grisha On Mon, 28 Jan 2002, Lewis Bergman wrote: > > Another reason could be that the getopt code from the Python 2.2 > > library is actually executed by an older Python interpreter that > > doesn't know of list comprehensions. > > It seems that this explanation is correct. I had installed python2.2 on this > machine with the make altinstall command as it is a RH7.2 install. simply > using make install breaks all kinds of things including printing. > > So, somehow, even though the instructions were followed completely and the > --with-python switch was pointing to the right place, the make install was > somehow using the other 1.5.2 install of python. > > I used a spare machine, installed python2.2 as the only python and it worked. > curious. > > I do get an error about mod_python being compiled without -DEAPI though. Is > this something to worry about? Perhaps I forgot to compile 2.2 with the > --with-threads=no option and this caused it? > -- > Lewis Bergman > Texas Communications > 4309 Maple St. > Abilene, TX 79602-8044 > 915-695-6962 ext 115 > > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://www.modpython.org/mailman/listinfo/mod_python >
|