Can anyone point out the pros and cons of TG2 over Django?
Last I checked, django has a very poor data implementation.  And that's a huge weakness in my book.  Django's orm doesn't allow me to use the power of the underlying database.  For example I can't use compound primary keys, which are important to good db design.  It also doesn't support more than a single database, which is not a big deal until you really need it and find that you can't do it without resorting to doing it manually.  Lastly if you have to make changes to your database structure in a team-friendly way, you have to try to choose between a set of 3rd party migration tools.
Turbogears seems to be more architecturally sound, doing its best to integrate individual tools that are awesome in their own right.  And because TG is more of an integrator, you're able to switch out pieces to suit your preferences.  Don't like SQL Alchemy? You can use SQLObject.  Don't like Genshi templates? You can use Mako or even django's, although you're not exactly stuck with the default on django either.
Time for tg2's cons:

TG has a much smaller community, and community usually has its benefit.
Django has a much better name.  I really like that name ;-)
Django seems simpler for the beginning web developer, with pretty cool admin tools.
TG has decent documentation, but you also need to go to Genshi's site to learn Genshi, SQL Alchemy's site to learn that, etc.  Django has great docs.

My 2 cents.
Django is my favorite python web framework. I've tried out others like pylons, web2py, nevow and others.
But I've never looked into TurboGears with much enthusiasm.
Now with TG2 out of beta I may give it a try. I'd like to know what are some of the pros and cons compared to Django.