It's mostly a matter of preference, but one detriment of Mako is that it does
not yet have a "renderer" implementation that works inside repoze.bfg. This
means you can't create a view that uses Mako as a "renderer", e.g.
@bfg_view(renderer='templates/foo.mak')
def myview(request):
return {'a':1}
... but you can do that with Chameleon. Until someone comes along and makes a
renderer implementation for Mako, at least.
- C
subscripti...@elliotgage.com wrote:
> Hoping to avoid a mini holy war here, but I am a bit torn on using mako
> or chameleon. I see some features that I like in both, but haven’t used
> either enough to really be able to make a fully edumacated decision.
>
> My application is a ground up shopping cart application, nothing too
> atypical about it.
>
>
>
> Am interested in others’ thoughts on the matter.
>
>
>
> Thanks,
>
> Elliot
>
>
>
>
> ___
> Repoze-dev mailing list
> Repoze-dev@lists.repoze.org
> http://lists.repoze.org/listinfo/repoze-dev
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
