I don't know officially, but Chameleon was added a lot earlier and the code may be inherited from BFG. Mako was added for the Pylons integration because Chameleon would have been too big a change for them. At the time it was thought that these would be the built-in template engines and others would be third-party. Since then mcdonc has talked about spinning those off too, as pyramid_chameleon and pyramid_mako, but that hasn't happened yet.
On Wed, Mar 27, 2013 at 10:44 AM, Jonathan Vanasco <jonat...@findmeon.com>wrote: > looking at the source, I see: > > * pyramid/chamelon_text.py > * pyramid/chamelon_zpt.py > * pyramid/mako_templating.py > > was there any reason for these being on the top-level, and not under a > consolidated namespace like pyramid/templating , or did this just > happen randomly ? > > -- > You received this message because you are subscribed to the Google Groups > "pylons-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-devel+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
