Carlos de la Guardia created zope.pagetemplate bindings for bfg the other day
(http://svn.repoze.org/repoze.bfg.zopepagetemplate/trunk/). I might try to
change that if it doesn't have what you need to get ZPT support, and then, if
necessary, create another package that has the other helper utils you've
In general, naming something repoze.bfg.gae would make sense if the package
really was only related to GAE, but bindings to zope.pagetemplate are useful
outside the context of GAE too, so I probably wouldn't put those bindings in a
package with "gae" in the name. Also, since what you're creating is probably a
BFG-related package, I'd expect a "repoze.bfg.gae" instead of "repoze.gae"
(repoze.bfg is a namespace package, used for packages related to BFG; "repoze"
is also a namespace package but contains packages not related to BFG).
I can get you access to the repoze SVN repository if you'd like to become a
On 5/4/09 9:00 PM, Tim Hoffman wrote:
> I am new to the list (and pretty new to repoze) I have put together a
> module which includes bindings for zope.pagetemplate with direct
> support for metal macros, plus a bunch of helper utils that make
> things a bit easier when using google app engine,
> I was thinking of calling it repoze.gae.
> A couple of question
> 1. does the naming make sense from the repoze communities point of view
> 2. should I split the page template handling into a seperate module
> from the utilities,
> 3. where should I put this stuff for people to get to ?
> Repoze-dev mailing list
Repoze-dev mailing list