Hi Hanno<div><br></div><div>Actually went back and had a look at my appengine instances, and the earliest one using zope.pagetemplate has been running </div><div>since Aug, 2008 ;-)</div><div><br></div><div>T</div><div><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
It might be easier to switch to the new kid, instead of trying to make<br>
the highly integrated zope.pagetemplate work for you.<br>
<div><br></div></blockquote><div><br></div></div><div>Its already been working since very early 2009 so it&#39;s more about being able to setup buildout etc..... rather than hand crafting everything.</div><div class="im">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
&gt; So now for my modest proposal,  do you think it would be feasible to move<br>
&gt; the restricted engine implementations out of zope.pagetemplate.engine and<br>
&gt; into some higher level package and provide a simple trusted engine that<br>
&gt; anyone can use (that supports metal as well)<br>
<br>
</div>At least Zope2 depends on this engine, so moving the engine out into a<br>
zope.app.* package is not an option, it would have to be some new<br></blockquote></div></div></blockquote></div></div>