On 1/18/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote:
It looks like there is some issue with classes, as they are being constructed, refering to classes that don't yet exist. That is only my take on the traceback, I cannot reproduce it on either of my machines.
The simple solution is to change the kidsupport.py to kid.load_template instead of kid.import_template. But this will stop base classes from reloading. I have not changed this because of the mixed reports I am receiving. Some have the issue and some don't. I have not been able to narrow down what particular components are different between the two groups.
As a temporary stop gab measure we could make it configurable. If the kid.reloadbases = True then do it otherwise do it the old way.
-- David
That may (or may not) fix this problem, but I would like to eliminate
that variable.
It looks like there is some issue with classes, as they are being constructed, refering to classes that don't yet exist. That is only my take on the traceback, I cannot reproduce it on either of my machines.
The simple solution is to change the kidsupport.py to kid.load_template instead of kid.import_template. But this will stop base classes from reloading. I have not changed this because of the mixed reports I am receiving. Some have the issue and some don't. I have not been able to narrow down what particular components are different between the two groups.
As a temporary stop gab measure we could make it configurable. If the kid.reloadbases = True then do it otherwise do it the old way.
-- David
