I would be +1 on splitting this up to pyramid_chameleon and pyramid_mako. But that's almost certainly because I have no use for either of those templating languages and for my specific work they sort of feel like bloating pyramid core.
That being said, their presence doesn't cause any real problems for me... the only place where this could be detrimental that I could see is someone deploying on something like Google App Engine. - Rocky On Friday, March 4, 2011 2:09:30 PM UTC-3:30, Chris McDonough wrote: > > Of these, the only ones to very easily *not* install would be Mako, > Chameleon, PasteScript, Paste, and PasteDeploy. The others are core > dependencies that really can't very easily be externalized. > > Doing that would take us down to 13 dependencies. We could indeed make > "pyramid_chameleon" and "pyramid_mako" and "pyramid_paste" packages to > restore the functionality for users of those dependencies. > > Would that actually service any particular goal? Would having fewer > "rails" in the core actually make anybody happier? > > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
