I'm not sure I understand what exactly "large" means. Some packages require configuration or extra work to be deployed. Breve does not require anything beside being imported and used. And I can't imagine how using it could interfere with using other packages/template engines.
I do understand that when you work on a library you should try to avoid unnecessary dependencies. But Pyramid itself was built on idea of re-using packages and that proved to be a great idea. Finding a balance was never an easy job. On Wednesday, January 1, 2014 10:07:02 PM UTC-4, Mike Orr wrote: > > On Wed, Jan 1, 2014 at 3:59 PM, askel <[email protected] <javascript:>> > wrote: > >> would add a dependency to a whole template language > > > > I'm afraid, avoiding dependency on some package by baking your own is > > otherwise called "reinventing the wheel" > > Except when you depend on something large to avoid writing something > small. If I depend on Breve, then everybody who uses WebHelpers2 would > have to depend on Breve also, even if they didn't want to. It's one > thing if you're writing a brand-new library, but another thing if > you're updating a library that's eight years old and already widely > used in a wide variety of programs (some web-based and some not), and > which heretofore has not depended on a template library I did make it > depend on Markupsafe, because that just does one small thing well. > Breve would be a larger commitment, and I'm not sure I want to go that > way, even though I do like Breve in some ways. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
