On 6/6/06, mikl <[EMAIL PROTECTED]> wrote: > That beeing said, the TG API hasn't been set in stone yet. Not until TG > 1.0 will we have complete API stability. For myself, I can only say > that I've looked at both TG and Django, and I've come to the conclusion > that TG has much more promise, even if it's not as complete as Django > is... yet :)
While "set in stone" is a very strong phrase, I will say that the TG API is effectively frozen for 1.0. We might *add* minor features, but there are no more breaking changes planned. As for SQLAlchemy vs. SQLObject, you can really only choose SQLAlchemy today if you're willing to dive into TG source and go along with potential breakage on the SQLAlchemy side. If *I* were about to start a new project, I would choose SQLAlchemy, but that's because I'm comfortable fixing things in TG. Once the support has solidified a bit and some basic docs written, I think SQLAlchemy will be a good choice. Note, though, that it will be a while before you get something like CatWalk or Model Designer for it. Unless you write it yourself, that is :) Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
