Received: by 10.101.126.13 with SMTP id d13mr5854216ann.23.1334135581544;
        Wed, 11 Apr 2012 02:13:01 -0700 (PDT)
X-BeenThere: turbogears-trunk@googlegroups.com
Received: by 10.236.140.106 with SMTP id d70ls1190628yhj.6.gmail; Wed, 11 Apr
 2012 02:13:00 -0700 (PDT)
Received: by 10.236.76.133 with SMTP id b5mr19726398yhe.0.1334135580700;
        Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
Received: by 10.236.76.133 with SMTP id b5mr19726395yhe.0.1334135580690;
        Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
Return-Path: <clsdan...@gmail.com>
Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54])
        by gmr-mx.google.com with ESMTPS id k54si1847458yhh.5.2012.04.11.02.13.00
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
Received-SPF: pass (google.com: domain of clsdan...@gmail.com designates 209.85.213.54 as permitted sender) client-ip=209.85.213.54;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of clsdan...@gmail.com designates 209.85.213.54 as permitted sender) smtp.mail=clsdan...@gmail.com; dkim=pass header...@gmail.com
Received: by yhgm50 with SMTP id m50so346479yhg.41
        for <turbogears-trunk@googlegroups.com>; Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=dqW5vEdJ607Kjf60V2Q+Yt/3I9LUKDncNbmmqQlSiik=;
        b=s/jbH6+K3tLzkFPf1JWegIMXFO51M+IDsDglQzyEOEaQfPp63/79AwD6mvrUG4z7Kj
         IB4RokeHaVj7CgddL8L1wNp3kMITvNzkivpcDcFTb4OgxImIZlL1vDPNI7JW9ZatLC+1
         n90gJMIcI5paMP7jPEaMs5rWPNmptNN5KUdtNeO+jufqYE+iVgGUqarKD+Skual5mRDx
         Ejoaa51YYUsJnhx9u5ZV7Z75hhNsN64fvWowKaEFisNpJGpqYB6+WkZ64HvOJCtDE8pn
         Q2yCxO/wWe7CCSk9TvNb0Z78F2lfvCCCuTqDSszD7Ar17ftNNH1gbr3tIfSjoLMIcjO3
         sx9A==
MIME-Version: 1.0
Received: by 10.236.185.10 with SMTP id t10mr12273275yhm.112.1334135580611;
 Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
Received: by 10.146.158.20 with HTTP; Wed, 11 Apr 2012 02:13:00 -0700 (PDT)
In-Reply-To: <CANijxxgRRoseVczd7PDw-4Npgiwi2m=ztYzB-jCCYs1hdUC...@mail.gmail.com>
References: <CANijxxgRRoseVczd7PDw-4Npgiwi2m=ztYzB-jCCYs1hdUC...@mail.gmail.com>
Date: Wed, 11 Apr 2012 02:13:00 -0700
Message-ID: <CAEF3qbkWAg_qdA5QjWhGPefuEiADhuqNDLwKGruf=A3SWgE...@mail.gmail.com>
Subject: Re: [tg-trunk] TurboGears 2.2 Beta
From: Carlos Daniel Ruvalcaba Valenzuela <clsdan...@gmail.com>
To: turbogears-trunk@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

Great :)

I trowed the templating benchmark at it just for fun and the
performance improvements are starting to show, can't wait for 2.3:

http://blog.blackchairsoft.com/2012/04/11/turbogears-2-2-beta-benchmarking/

While benchmarking it caught my attention that when using Jinja
quickstart template TG will complain that only Genshi and Mako are
supported under TG, which really only means that we need to have
either Genshi or Mako loaded too for other things besides the
application templates (which can be in Jinja with no problems).

That warning got me thinking that maybe I should also load Mako with
Jinja, I'm not really sure if not loading another template system can
hurt other functions such as TW, but I'm under the impression that the
TW integration code sets the TW templates to either Mako or Genshi
depending on what we have loaded.

Any ideas on that?

Regards,
Carlos Daniel Ruvalcaba Valenzuela