> But it will provoke the same anxiety, it will leave those of us behind that > have existing TG2 installations (let alone TG1). And please don't pretend > there will be a reasonable stable way to make the next big thing backwards > compatible. TG1 vs. TG2 has proven enough that this is harder than one might > think, and it's debatable if it is a worthy goal.
Well, the backwards compatibility story will be done completely differently than the tg1 to tg2 approach. The current code has support for putting an existing TG2 app *as is* into the pyramid, and letting URL's be overridden by whatever you do in the Pyramid app. That way there's no need to change stuff that works, and if you want to make use of the new stuff in pyramid you can do that at the same time. And if there's value to you in the migration of controller code to pyramid, then you can do that too. Ultimately we plan to support TG1 to Pyramid migrations in exactly the same way (via the legacy handler). And obviously we will continue to provide bugfixes and support for TG2 and TG1 applications in the wild. --Mark Ramm P.S. Nothing is yet decided, this is the time to raise warning flags, issues, and objections so that we can decide what we want to do as a community. -- 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.
