There should not be modules loaded that will never be used, but sometimes you may not reallize where they are used in a default install or by one of our components ;)
It's possible to put the imports inside a function call or an if statement, but it's only worth doing if your app will really work without those things, and we've taken some care to do that in many places. But I'm sure there is more that we could do -- but honestly we use a lot of stuff, and our memory footprint is not out of control. Many of the modules you see loaded are part of the python standard library. IF there are libraries that are not needed by most folks, and we can make them optional we will do that, but rather than spend a lot of time on that (I don't much need to reclaim every last possible kb of memory) I expect that we'll continue making things faster, adding features, and working on improving what we have. But, if you have specific questions about specific things that are loaded, we'll do our best to point you in the right direction to find the answers ;) --Mark On Wed, May 27, 2009 at 8:46 PM, AF <[email protected]> wrote: > > > > 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 > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
