I may be biased, since I've paid more attention to Kid, SQL Object and the "current turbogears" than I have the "future". But I think the future is the future, and the present belongs to SQLObject and Kid.
SO and Kid are good enough for most web applications most of the time. Not only that, if you stay with the defaults, you'll find better documentation, better tested projects, and you'll get a defined upgrade path when the future comes. On the other hand, I love SQLAlchemy, and if you have complex, legacy databases, you will too. Genshi is very nice but the cases where you _need_ it over Kid are much fewer and farther between. So, in spite of the prevailing wisdom on the list, I'd say go with the defaults unless you have a reason not to. --Mark Ramm On 1/8/07, gasolin <[EMAIL PROTECTED]> wrote: > > I think it's a good point to be well discussed in the incoming doc > sprint, > and produce some solid guide about the discussion result. > > It's time to do something for this situation. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
