> There is potentially a gotcha with this - now the framework needs to be > directly aware of things like the session handling middleware. In the > previous arrangement, indiviudal projects were, but the framework itself > was not. And if the framework needs to be aware of it, should it have > them as dependencies? If so, that could be a killer for minimal installs. > > I'm not against what you've proposed - it certainly has advantages - > just want to be sure we're aware of the downsides too.
This is true enough. We can wrap some of the middleware pieces in if statements and only import the modules is they user actually wants them. And there's nothing stopping users who want to maximize control of their stack setup from doing this manually in their project. We may even want to explicitly support and document that. But at the same time I don't want all this config/setup code to get in the way for people who are just getting started. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
