> >There's been talk about a tg-dev package, which would contain tools > >for developing turbogears projects. The thought behind this is > > > > > I think it's a good idea. > > One possibility as well, is to the make the core not dependent on any > particular ORM, template language, auth* system, etc. But tg-dev would > be dependent on the more common choices, so you could get started > developing quickly, without having to separately install loads of > dependencies.
My question with this is, should we take some of the WSGI stack and environment setup out of the paster template, and move it into the framework. If we do this, it should be done with a couple of functions which setup the SQLAlchemy environment, and wrap your app in all the "required" middleware, etc. That way people who want to customize things can do it manually, rather than calling the setup functions, but people who just use those functions can automatically update their environment/middleware stack when we make changes -- without the need to edit their template. The reason I'm thinking about this is that one of the complaints I've heard about Pylons is that it is difficult to upgrade from one version to the next because so many template changes are required. And I'd like to insulate users from that a bit. These setup functions would probably add an SQLAlchemy requirement for those who use them, but would not make it a general framework requirement. We could wrap the SA imports in try: except and warn users that they have to setup manually if SA isn't installed. --Mark --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
