Gregory Trubetskoy
grisha at modpython.org
Thu Jun 15 07:44:04 EST 2000
Sounds to me like the mod_python package is not in your pythonpath. BTW, the win32 binary is unstable because of some thread problems. 2.4 should be considerably more stable and will come out in a couple of days. Grisha On Thu, 15 Jun 2000, Martin Jenssen wrote: > Hello, > > I am getting some strange messages when trying to setup Apache with > mod_python on Windows NT. I used the precompiled binary of mod_python 2.2 > as found on http://www.modpython.org/, the precompiled binary of Apache > 1.3.12 as found on http://www.apache.org/ and Windows NT 4.0 Server. > > When I try to start Apache with mod_python configured as specified in the > documentation, I get these messages: > > """ > make_obcallback(): could not import mod_python.apache. > make_obcallback(): could not call init. > Apache/1.3.12 (Win32) mod_python/2.2 Python/1.5.2 running... > """ > > Strangely, it doesn't quit, but continues to try to serve web pages. For > each .py file I try to reach via the web browser, I get these messages > thrown into the error.log file: > > """ > [Thu Jun 15 10:37:45 2000] [error] [client 193.71.134.144] \ > python_handler: get_obcallback returned no obCallBack! > """ > > > Martin Jenssen > > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://www.modpython.org/mailman/listinfo/mod_python >
|