[mod_python] What's the deal with _apachemodule?

Adrien Plisson rien at yeepa.org
Sat Apr 13 22:58:19 EST 2002


From: "Markus Demleitner" <msdemlei at cl.uni-heidelberg.de>
> ...
> So, what's the deal?  _apachemodule.so isn't mentioned anywhere in the
> source tree, but it seems to be required to satisfy the import _apache
> statement.  What might the solution to this riddle be?

if i remember right, this problem is due to the fact the the _apache module
works *only* in an apache environment, that is, only when imported in a
module which is called from mod_python which runs on a launched apache
server.

quoted from the doc:
"4.3 apache - Access to Apache Internals.

The Python Application Programmer interface to Apache internals is contained
in a module appropriately named
apache, located inside the mod python package. This module provides some
important objects that map to Apache
internal structures, as well as some useful functions, all documented below.
The apache module can only be imported by a script running under mod python.
This is because it depends on a
built-in module apache provided by mod python."

here it is, don't try to test mod_python from a standalone script.

i hope i 'd been helpful.

--
rien




More information about the Mod_python mailing list