On 1/25/2011 9:40 AM, Christoph Zwerschke wrote: > Am 25.01.2011 14:42, schrieb Tamas Hegedus: >> E.g. I would not worry about TG2 w/o a maintainer if I knew that I can >> continue developing using the current TG2 and I will be able to use TG3 >> w/o any extra work or loss of some functionality when TG3 is released. > I think you misunderstand the idea of TG3. It's to build something new > based on Pyramid that is in the spirit of TG and so that TG projects can > be easily migrated, but not to create something that 100% emulates TG2 > with all of its quirks and peculiarities so you don't have *any* extra > work. That would not make much sense since it would be easier to > continue maintaining TG2 then. > > -- Christoph > I am new to TG and have found the most recent discussion on this list interesting.
I recently have spent a little time with tg2 which seems great as a full stack project for database oriented apps, particularly for programmers like myself with only modest skills. I just build things for use in my own small business. >From what I have read recently it seems that the various python app frameworks are converging which seems like a good thing. But in terms of tg2 in particular, based on the current thread., I am confused about the differences and choices involving TG2, TG3, pylons, pyramid and the various trade offs and the choices involved. With no legacy projects to maintain, and considering my modest skills, any thoughts on which code base I i should be investing my time on? Mark B -- 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.
