[mod_python] Trouble with multiple class objects in publishermodel

Martin Stoufer wrote ..
> This was part of the debugging process to verify that things were 
> actually getting instantiated and still in scope.
> 
> I brushed off some python black art debug tricks and found that the 
> secondary DomProdLibOutput module was being cached and not properly 
> unloaded/loaded when I modified it or the Dom class.
> 
> A quick restart of Apache resolved all problems and I'm clean sailing again.
> I didn't see any docs showing how we can force a reload/re byte-compile
> of a module.

Module reloading is a bit of a black art with the version of mod_python you
are using. The module importer in mod_python 3.3 has been reimplemented
and hopefully will be more predictable and be able to cope better with
automatic module reloading.

Anyway, at least you worked out the problem.

Graham

> Graham Dumpleton wrote:
> > Martin Stoufer wrote ..
> >   
> >> Well events are getting better/worse. It seems that when _generate()
> is
> >> called, it is now unable to properly invoke the method it is calling.
> >> I've successfully returned/logged the string representation of both
> >> self._output and self._output.generate. They reference what they should
> >> be. Am I using reserved mod_python variable names?
> >>
> >> ...
> >>
> >>   def _generate(self):
> >>         #_result = self._output.generate()
> >>         _result = str(self._output.generate)
> >>     
> >
> >     _result = str(self._output.generate())
> >
> > You weren't invoking the method, you were turning a reference to it
> > into a string.
> >
> >   
> >>         self._req.log_error("Result from Html() %s" % _result, 
> >> apache.APLOG_NOTICE)
> >>         return _result
> >>     
> 
> -- 
> * Martin C. Stoufer              *
> * DIDC/DSD/ITG                   *
> * Lawrence Berkeley National Lab *
> * MS 50B-2215 510-486-8662       *