[The following behaviour occurs with 0.1.0 and the latest trunk checked
out of SVN].

The turbogears example project still blows up -- when attempting to
render the widget at the bottom of the welcome.html template. I've been
batting this around on and off the whole day with little luck -- any
insights ??

Tnx

Alanl

------------------

Traceback (most recent call last):
  File
"c:\python24\lib\site-packages\cherrypy-2.2.1-py2.4.egg\cherrypy\_cphttptoo ls.py",
line 105, in _run
    self.main()
  File
"c:\python24\lib\site-packages\cherrypy-2.2.1-py2.4.egg\cherrypy\_cphttptoo ls.py",
line 254, in main
    body = page_handler(*virtual_path, **self.params)
  File "<string>", line 3, in index
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\contro llers.py",
line 331, in expose
    output = database.run_with_transaction(
  File "<string>", line 5, in run_with_transaction
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\databa se.py",
line 245, in so_rwt
    retval = func(*args, **kw)
  File "<string>", line 5, in _expose
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\contro llers.py",
line 348, in <lambda>
    mapping, fragment, *args, **kw)))
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\contro llers.py",
line 382, in _execute_func
    return _process_output(output, template, format, content_type,
mapping, fragment)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\contro llers.py",
line 74, in _process_output
    fragment=fragment)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\view\b ase.py",
line 132, in render
    return engine.render(**kw)
  File "build\bdist.win32\egg\markup\plugin.py", line 65, in render
  File "build\bdist.win32\egg\markup\core.py", line 92, in render
  File "build\bdist.win32\egg\markup\output.py", line 338, in __call__
  File "build\bdist.win32\egg\markup\output.py", line 498, in next
  File "build\bdist.win32\egg\markup\output.py", line 443, in __call__
  File "build\bdist.win32\egg\markup\core.py", line 149, in _ensure
  File "build\bdist.win32\egg\markup\filters.py", line 147, in __call__
  File "build\bdist.win32\egg\markup\template.py", line 920, in
_flatten
  File "build\bdist.win32\egg\markup\template.py", line 957, in _match
  File "build\bdist.win32\egg\markup\template.py", line 892, in _eval
  File "build\bdist.win32\egg\markup\eval.py", line 86, in evaluate
  File
"C:\usr\python\markup\examples\turbogears\markuptest\templates\welcome.html ",
line 35, in <Expression "ET(widget.display())">
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\widget s\meta.py",
line 107, in lockwidget
    output = self.__class__.display(self, *args, **kw)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\widget s\forms.py",
line 51, in _update_path
    returnval = func(self, *args, **kw)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\widget s\forms.py",
line 225, in display
    return super(InputWidget, self).display(value, **params)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\widget s\base.py",
line 226, in display
    return view.transform(params, template=self.template_c)
  File
"c:\python24\lib\site-packages\TurboGears-0.9a8-py2.4.egg\turbogears\view\b ase.py",
line 137, in transform
    return engine.transform(info, template)
  File "build\bdist.win32\egg\markup\plugin.py", line 70, in transform
  File "build\bdist.win32\egg\markup\plugin.py", line 55, in
load_template
AttributeError: type object 'Template' has no attribute 'rfind'

Hi Alanlit,

Am 16.08.2006 um 23:32 schrieb Alanlit:

I had the same problem, and Matt Good gave me the following advice:

 > You'll need to grab it from the TG 1.0 branch.  TurboGears widgets
 > assumed Kid was the default template engine, so I had to make a
 > change to their code so they specifically loaded the Kid engine
 > instead of the default.

This fixed the issue for me.

(Apparently, trunk != 1.0 branch in the TG repos, even though 1.0  
hasn't been released yet. And why this issue isn't fixed on trunk I  
don't know.)

Cheers,
Chris
--
Christopher Lenz
   cmlenz at gmx.de
   http://www.cmlenz.net/

Chris,

   and here was I blaming windows. It comes with being on the bleeding
edge I guess. Anyway, latest (from 1.0 though it claims it is 0,9a9) TG
checked out and the demo turbogears project works out of the Markup
box.

Tnx !

Alanl

On Aug 16, 2006, at 5:50 PM, Christopher Lenz wrote:

We froze TG 1.0 from experimental changes a few weeks ago, which is  
why trunk != 1.0. The fact that this is fixed on 1.0 and not trunk  
means that someone forgot to merge.

Kevin

Should that "someone" be me?  I'm not quite clear on the merging policy
for the TG branches yet.

-- Matt Good

On Aug 20, 2006, at 2:09 PM, Matt Good wrote:

That's what we've been doing... each person would commit to 1.0 and  
then merge to trunk. We should be flipping that around soon as 1.0  
starts taking just fixes.

Kevin