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.
在过去的几年里，我一直在用Turbogears 1来为小网站做原型，而且它的牙齿已经长了一些。对于升级到Turbogears 2或者转换成Django之类的东西，有什么建议吗?我在熟悉TG社区和使用Django的更大的社区之间左右为难。我非常喜欢内置的CMS功能和谷歌应用程序引擎支持。
Any advice?
任何建议吗?
Thanks
谢谢
.M.
打烊。
6 个解决方案
#1
10
I have experience with both Django and TG1.1.
我对Django和TG1.1都有经验。
IMO, TurboGears strong point is it's ORM: SQLAlchemy. I prefer TurboGears when the database side of things is non-trivial.
在我看来，涡轮齿轮的强项是ORM: SQLAlchemy。当数据库方面的内容非常重要时，我更喜欢使用TurboGears。
Django's ORM is just not that flexible and powerful.
Django的ORM并不那么灵活和强大。
That being said, I prefer Django. If the database schema is a good fit with Django's ORM I would go with Django.
也就是说，我更喜欢《被解救的姜戈》。如果数据库模式很适合Django的ORM，那么我将使用Django。
In my experience, it is simply less hassle to use Django compared with TurboGears.
在我的经验中，使用Django与TurboGears相比就简单多了。
#2
13
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 .
TG2是建在高架上，也有相当大的社区。与TG1相比，TG更快了，它包含了每个方法(不仅仅是web页面)的缓存引擎。我认为它比Django更适合ajax，顺便说一下，页面可以轻松地以HTML或JSON格式发布。
2011 update: after 3 years of bloated frameworks I'm an happy user of http://bottlepy.org/
2011年更新:经过三年臃肿的框架，我是http://bottlepy.org/的快乐用户
#3
5
I have been using Django for a year now and when I started I had no experience of Python or Django and found it very intuitive to use.
我已经使用Django一年了，当我开始使用它的时候，我没有使用Python或Django的经验，并且发现使用它非常直观。
I have created a number of hobbyist Google App Engine apps using Django with the latest one being a CMS for my site. Using Django has meant that I have been able to code a lot quicker and with a lot less bugs.
我使用Django开发了许多爱好者谷歌应用程序引擎应用程序，最新的一个是我的站点的CMS。使用Django意味着我可以更快地编写代码，而且bug更少。
#4
1
Am sure you would have read from plenty of comparison between TurboGears and DJango on web.
我敢肯定你会在web上读到关于TurboGears和DJango的大量比较。
But as for your temptation on CMS and GAE, i can really think you got to go DJango way. Check these out, and decide youself.
但是关于你对CMS和GAE的诱惑，我真的认为你应该走DJango的路。看看这些，然后自己决定。
Django与GAE
Django的CMS
#5
0
TG2 seem much complicated and confusing, even for doing somewhat simple like a login page with multimple error messages How to extend the Turbogears 2.1 login functionality I think thats because of intemperance in modularity...
TG2看起来非常复杂和令人困惑，即使做一些简单的事情，比如一个登录页面，有多个错误消息，如何扩展Turbogears 2.1登录功能，我认为这是因为模块化的不稳定性……
#6
-1
Ive only got one question...is the app you are developing directed towards social networking or customized business logic?
我只有一个问题……你正在开发的应用是针对社交网络还是定制的业务逻辑?
I personally find Django is good for social networking and pylons/turbogears if you really want the flexibility and no boundaries...
我个人认为Django对社交网络和pylons/turbogears有好处，如果你真的想要灵活性和无边界…
just my 2c
只是我的2摄氏度
#1
10
I have experience with both Django and TG1.1.
我对Django和TG1.1都有经验。
IMO, TurboGears strong point is it's ORM: SQLAlchemy. I prefer TurboGears when the database side of things is non-trivial.
在我看来，涡轮齿轮的强项是ORM: SQLAlchemy。当数据库方面的内容非常重要时，我更喜欢使用TurboGears。
Django's ORM is just not that flexible and powerful.
Django的ORM并不那么灵活和强大。
That being said, I prefer Django. If the database schema is a good fit with Django's ORM I would go with Django.
也就是说，我更喜欢《被解救的姜戈》。如果数据库模式很适合Django的ORM，那么我将使用Django。
In my experience, it is simply less hassle to use Django compared with TurboGears.
在我的经验中，使用Django与TurboGears相比就简单多了。
#2
13
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 .
TG2是建在高架上，也有相当大的社区。与TG1相比，TG更快了，它包含了每个方法(不仅仅是web页面)的缓存引擎。我认为它比Django更适合ajax，顺便说一下，页面可以轻松地以HTML或JSON格式发布。
2011 update: after 3 years of bloated frameworks I'm an happy user of http://bottlepy.org/
2011年更新:经过三年臃肿的框架，我是http://bottlepy.org/的快乐用户
#3
5
I have been using Django for a year now and when I started I had no experience of Python or Django and found it very intuitive to use.
我已经使用Django一年了，当我开始使用它的时候，我没有使用Python或Django的经验，并且发现使用它非常直观。
I have created a number of hobbyist Google App Engine apps using Django with the latest one being a CMS for my site. Using Django has meant that I have been able to code a lot quicker and with a lot less bugs.
我使用Django开发了许多爱好者谷歌应用程序引擎应用程序，最新的一个是我的站点的CMS。使用Django意味着我可以更快地编写代码，而且bug更少。
#4
1
Am sure you would have read from plenty of comparison between TurboGears and DJango on web.
我敢肯定你会在web上读到关于TurboGears和DJango的大量比较。
But as for your temptation on CMS and GAE, i can really think you got to go DJango way. Check these out, and decide youself.
但是关于你对CMS和GAE的诱惑，我真的认为你应该走DJango的路。看看这些，然后自己决定。
Django与GAE
Django的CMS
#5
0
TG2 seem much complicated and confusing, even for doing somewhat simple like a login page with multimple error messages How to extend the Turbogears 2.1 login functionality I think thats because of intemperance in modularity...
TG2看起来非常复杂和令人困惑，即使做一些简单的事情，比如一个登录页面，有多个错误消息，如何扩展Turbogears 2.1登录功能，我认为这是因为模块化的不稳定性……
#6
-1
Ive only got one question...is the app you are developing directed towards social networking or customized business logic?
我只有一个问题……你正在开发的应用是针对社交网络还是定制的业务逻辑?
I personally find Django is good for social networking and pylons/turbogears if you really want the flexibility and no boundaries...
我个人认为Django对社交网络和pylons/turbogears有好处，如果你真的想要灵活性和无边界…
just my 2c
只是我的2摄氏度