Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Sean Dague
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 OpenStack from my recollection,
I think that's probably the prefered thing to consolidate on.

Alembic being different is fine, it's a dependent library.

-Sean

 mark
 
 
 On Feb 2, 2015, at 3:13 PM, Sean M. Collins s...@coreitpro.com wrote:

 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

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 


-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Mark McClain
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 s...@coreitpro.com wrote:
 
 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
 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Sean M. Collins
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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Mike Bayer


Sean Dague s...@dague.net wrote:

 On 02/02/2015 06:06 PM, Mike Bayer wrote:
 Sean Dague s...@dague.net 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 more used in other parts of OpenStack from my recollection,
 I think that's probably the prefered thing to consolidate on.
 
 Alembic being different is fine, it's a dependent library.
 
 
 there’s no reason not to have both installed. Tempita also gets 
 installed with a typical openstack setup.
 
 that said, if you use Mako, you get the creator of Mako on board to help as 
 he already works for openstack, for free!
 
 Sure, but the point is that it would be better to have the OpenStack
 code be consistent in this regard, as it makes for a more smooth
 environment.

stick with Jinja if that’s what projects are already using.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Mike Bayer


Sean Dague s...@dague.net 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 more used in other parts of OpenStack from my recollection,
 I think that's probably the prefered thing to consolidate on.
 
 Alembic being different is fine, it's a dependent library.


there’s no reason not to have both installed. Tempita also gets installed 
with a typical openstack setup.

that said, if you use Mako, you get the creator of Mako on board to help as he 
already works for openstack, for free!




 
   -Sean
 
 mark
 
 
 On Feb 2, 2015, at 3:13 PM, Sean M. Collins s...@coreitpro.com wrote:
 
 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
 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 -- 
 Sean Dague
 http://dague.net
 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

2015-02-02 Thread Sean Dague
On 02/02/2015 06:06 PM, Mike Bayer wrote:
 
 
 Sean Dague s...@dague.net 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 more used in other parts of OpenStack from my recollection,
 I think that's probably the prefered thing to consolidate on.

 Alembic being different is fine, it's a dependent library.
 
 
 there’s no reason not to have both installed. Tempita also gets installed 
 with a typical openstack setup.
 
 that said, if you use Mako, you get the creator of Mako on board to help as 
 he already works for openstack, for free!

Sure, but the point is that it would be better to have the OpenStack
code be consistent in this regard, as it makes for a more smooth
environment.

-Sean

-- 
Sean Dague
http://dague.net



signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev