On May 27, 6:41 pm, cd34 <[email protected]> wrote:
> I look at TurboGears as glue for a number of well-written/well-
> supported libraries.
>
> You could do everything yourself direct with pylons, and load
> formencode, and some widget library and other libraries that you need,
> but, the TG2 framework (and presumably TG1) pulls those modules in and
> for better or worse, their dependencies. What you end up with is a
> framework that is more a collection of working parts that may not be
> as optimized as hand picking everything, but, it is infinitely more
> maintainable because they are able to pull in libraries without having
> to apply patches each time.
Sure I realise the baggage that can come with a framework.
I was asking from more of a Python programming style point of
view....
I assume that TG1/TG2 are well written Python apps. Why do all sorts
of modules that we know will never (ever) be used get called in?
Is it a python limitation? An established style of coding issue?
That is what I am curios about.
Thank you
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
