Hi David, I haven't been able to reproduce the problem by using kid
standalone. But then, i'm not really experienced in using Kid without
turbogears.
The simplest test case to reproduce this problem would be installing
turbogears and running: tg-admin toolbox I think:). Working trough the
code I have been able to track down the problem a bit further.
The python proces gets stuck at line 87 of importer.py :during the
following call in the load_template() method:
exec code in mod.__dict__
This after beeing called from __init__.py line 119:
mod = importer._create_module(code, name, filename, store=cache)
with:
code =
<code object ? at 012843A0, file
"c:\python24\lib\site-packages\turbogears-0.9a0dev_r229-py2.4.egg\turbogears\toolbox\main.py",
line 1>
name = turbogears.toolbox.main
filename =
c:\python24\lib\site-packages\turbogears-0.9a0dev_r229-py2.4.egg\turbogears\toolbox\main.kid
store = 1
The code object its self is created on line 118 by:
code = template.compile(dump_code=cache,
dump_source=os.environ.get('KID_OUTPUT_PY'))
with:
dump_code = 1
dump_source = None
template is a KidFile instance. But I'm a bit confussed about how the
KidFile.compile() and KidFile.code() combination works so thats where I
stoped tracing for now.
