The mod_python project is no longer developed and was moved into the ASF attic. It is no longer recommended that it be used and the last official release will not compile on current Apache versions. It only continues in any form because some Linux distros are making their own patches so it will compile. They can only ever keep this up for Apache 2.2 though, as 2.4 differences were too great and minor patches will not make it work there.
Graham On 6 February 2013 09:30, Mikhail T. <[email protected]> wrote: > On 05.02.2013 17:14, Graham Dumpleton wrote: > > In the next version of mod_wsgi though I am dropping support for > coexistence. I want to flag that fact with a big error message and refuse > to start up if both loaded. > > I'm not sure, how Python-users will react, but, as a Tcl-user, I'd hate to > be forced to choose one of the two modules. I'm hosting to completely > unrelated vhosts, which use the two Tcl-using modules. > > > On 05.02.2013 17:20, Jeff Trawick wrote: > > module *modp; > for (modp = ap_top_module; modp; modp = modp->next) { > foo(modp->name); > } > > Cool! I thought of relying on the fact, that server_rec's module_config is > a an array of module-pointers, but the above seems more reliable. Thank you! > > -mi > >
