spacetaxi wrote: > It seems that the best > solution would be to delay my project for half a year, to look > how/where TG (and Django) are going. ;-) Unfortunately, this isn't > possible.
That wasn't my point :) What I meant to say was just that you can easily utilize TG as it is, but you might have to to make changes to your code when you upgrade to the next version. I'm creating applications with TG and SQLObject now, although I realize I might have to convert it to SQLAlchemy later - but given the ease of deploying with TG in the first place, I don't think that's too much of a problem, especially if you take into consideration that although SQLAlchemy might be the future, SQLObject will still be supported in 1.0 and onwards. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
