Sean Dague wrote:
> On 02/02/2015 06:06 PM, Mike Bayer wrote:
>> Sean Dague wrote:
>>
>>> On 02/02/2015 04:20 PM, Mark McClain wrote:
You’re right that the Mako dependency is really a side effect from
Alembic. We used jinja for tempting radvd because it is used by the
projec
On 02/02/2015 06:06 PM, Mike Bayer wrote:
>
>
> Sean Dague wrote:
>
>> On 02/02/2015 04:20 PM, Mark McClain wrote:
>>> You’re right that the Mako dependency is really a side effect from Alembic.
>>> We used jinja for tempting radvd because it is used by the projects within
>>> the OpenStack
Sean Dague wrote:
> On 02/02/2015 04:20 PM, Mark McClain wrote:
>> You’re right that the Mako dependency is really a side effect from Alembic.
>> We used jinja for tempting radvd because it is used by the projects within
>> the OpenStack ecosystem and also used in VPNaaS.
>
> Jinja is far m
On 02/02/2015 04:20 PM, Mark McClain wrote:
> You’re right that the Mako dependency is really a side effect from Alembic.
> We used jinja for tempting radvd because it is used by the projects within
> the OpenStack ecosystem and also used in VPNaaS.
Jinja is far more used in other parts of Open
You’re right that the Mako dependency is really a side effect from Alembic. We
used jinja for tempting radvd because it is used by the projects within the
OpenStack ecosystem and also used in VPNaaS.
mark
> On Feb 2, 2015, at 3:13 PM, Sean M. Collins wrote:
>
> Sorry, I should have done a b
Sorry, I should have done a bit more grepping before I sent the e-mail,
since it appears that Mako is being used by alembic.
http://alembic.readthedocs.org/en/latest/tutorial.html
So, should we switch the radvd templating over to Mako instead?
--
Sean M. Collins
___
