Open Stack

Also, jinja2 is in requirements. We have no specific requirements on a particular version so feel free to pin it to a specific. We (trove) use it to generate config templates.

https://github.com/openstack/requirements/commit/96f38365ce94d2135f7744c93bae0ce92a747195

On Jul 16, 2013, at 1:10 PM, Nachi Ueno wrote:

> Hi folks
> 
> Jinja2 looks have +3.
> This is the winner?
> 
> # My code can be done by Jinja2 also.
> 
> so if we choose Jinja2, what's version range is needed?
> 
> Thanks
> Nachi
> 
> 
> 
> 2013/7/16 Matt Dietz <matt.dietz at rackspace.com>:
>> I'll second the jinja2 recommendation. I also use it with Pyramid, and
>> find it non-obtrusive to write and easy to understand.
>> 
>> -----Original Message-----
>> From: Sandy Walsh <sandy.walsh at RACKSPACE.COM>
>> Reply-To: OpenStack Development Mailing List
>> <openstack-dev at lists.openstack.org>
>> Date: Tuesday, July 16, 2013 11:34 AM
>> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
>> Subject: Re: [openstack-dev] Cheetah vs Jinja
>> 
>>> I've used jinja2 on many projects ... it's always been solid.
>>> 
>>> -S
>>> 
>>> ________________________________________
>>> From: Solly Ross [sross at redhat.com]
>>> Sent: Tuesday, July 16, 2013 10:41 AM
>>> To: OpenStack Development Mailing List
>>> Subject: [openstack-dev] [Change I30b127d6] Cheetah vs Jinja
>>> 
>>> (This email is with regards to https://review.openstack.org/#/c/36316/)
>>> 
>>> Hello All,
>>> 
>>> I have been implementing the Guru Meditation Report blueprint
>>> (https://blueprints.launchpad.net/oslo/+spec/guru-meditation-report), and
>>> the question of a templating engine was raised.  Currently, my version of
>>> the code includes the Jinja2 templating engine (http://jinja.pocoo.org/),
>>> which is modeled after the Django templating engine (it was designed to
>>> be an implementation of the Django templating engine without requiring
>>> the use of Django), which is used in Horizon.  Apparently, the Cheetah
>>> templating engine (http://www.cheetahtemplate.org/) is used in a couple
>>> places in Nova.
>>> 
>>> IMO, the Jinja template language produces much more readable templates,
>>> and I think is the better choice for inclusion in the Report framework.
>>> It also shares a common format with Django (making it slightly easier to
>>> write for people coming from that area), and is also similar to template
>>> engines for other languages. What does everyone else think?
>>> 
>>> Best Regards,
>>> Solly Ross
>>> 
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> 
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev