Turbogears 2 vs Django - any advice on choosing replacement for Turbogears 1?


I have been using Turbogears 1 for prototyping small sites for the last couple of years and it is getting a little long in the tooth. Any suggestions on making the call between upgrading to Turbogears 2 or switching to something like Django? I'm torn between the familiarity of the TG community who are pretty responsive and do pretty good documentation vs the far larger community using Django. I am quite tempted by the built-in CMS features and the Google AppEngine support.

Any advice?



7/13/2009 7:49:39 AM

Accepted Answer

I have experience with both Django and TG1.1.

IMO, TurboGears strong point is it's ORM: SQLAlchemy. I prefer TurboGears when the database side of things is non-trivial.

Django's ORM is just not that flexible and powerful.

That being said, I prefer Django. If the database schema is a good fit with Django's ORM I would go with Django.

In my experience, it is simply less hassle to use Django compared with TurboGears.

7/13/2009 10:18:12 AM

TG2 is built on top of Pylons which has a fairly large community as well. TG got faster compared to TG1 and it includes a per-method (not just web pages) caching engine. I think it's more AJAX-friendly than Django by the way pages can be easly published in HTML or JSON .

2011 update: after 3 years of bloated frameworks I'm an happy user of http://bottlepy.org/

Licensed under: CC-BY-SA with attribution
Not affiliated with: Stack Overflow