On Dec 25, 2007 2:36 PM, Nicolai Richter (Gm) <[EMAIL PROTECTED]> wrote:
> > Helper libs are fine if they're supported in the official > > documentation. TG and Pylons have a fundamentally different > > philosophy in this regard. They try to outsource as much as possible, > > and only write their own stuff if nothing external is adequate. > > What do you mean by official documentation? Of the mega-frameworks? Or > core python? This was in the context of webhelpers+formencode vs your scary CherryPy experiment. Webhelpers and formencode are Pylons dependencies and recommended in the official docs. SQLAlchemy and some other things are only in the user-contributed docs (the Cookbook) for now, but will be in the next version of the official docs though they won't be Pylons dependencies. The important point isn't whether they're homegrown, it's whether they're maintained and don't take a sudden direction contrary to the framework. By working closely with the developers of the other packages and being a significant "market" for them, you give them an incentive to remain quality and stable. It's not unlike the Linux kernel development, where different subsystems are maintained by different teams, and sometimes a popular driver remains outside the mainstream kernel for years. The difference is the kernel components "submerge" under a single brand name, whereas Pylons components don't. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
