Compare web2py and TurboGears
web2py was originally designed as a teaching tool, but it gained adoption outside of the academic world. It is a full-stack framework containing all the components needed to build fully functional web applications using the Model View Controller (MVC) pattern. Inspired by the Ruby on Rails and Django. It is not very popular right now but was ranked amongst top Python web frameworks in 2011.
TurboGears was born as a full stack layer on top of Pylons, and many other disparate libraries and middleware. It is now a standalone WSGI web framework designed around MVC architecture inspired by Ruby on Rails and provides all the features developes need for web development. It can also run in minimal mode and act like a microframework such as Flask.
Let's see how web2py and TurboGears compare on various factors and features and which to choose when.
Python full-stack for building web applications.
A full-stack web application framework for Python.
Not in use at any large company.
8 job openings which list web2py as a requirement.
3 job openings which list TurboGears in the job description.
Web2py takes a unique approach where models and controllers are executed in a single global environment, which is initialized at each HTTP request. While there are pros to this approach, such as developers never having to worry about cleaning up or avoid conflict between requests, the major disadvantage is that the code is models is executed with every request which carries a performance penalty.
Not as performant
as barebones or even fullstack frameworks. Extensions could impact performance adversely.
Not as flexible as microframeworks, but doesn't always get in the way.
Developers can use TurboGears as a microframework which is very flexible. However, as you start building towards a fullstack solution, it does expect things to be done in a certain way.
Ease of Learning
Limited online tutorials and resources, and many are several years old. The best resource for learning is web2py author's own "web2py Complete Reference Manual"
, which seems to be written in 2013.
Ease of Learning
Has a learning but since it uses a lot of exisitng 3rd party libraries it becomes are little easier to onboard. It also has a decent amount of tutorials online.
Ships with a Database Abstraction Layer (DAL) which supports MySQL, PostgreSQL, SQLite, and many other relational databases.
No built-in support. Very limited support for NoSQL databases. Currently, it only supports Google Datastore on the Google App Engine.
Supports MongoDB out of the box using Ming ORM
. Ming ORM was developed to look like SQLAlchemy so it's easier for developers familiar with SQLAlchemy to start using it.
Yes ships with a built-in admin panel.
Built-in admin panel.
Built-in protection against input injections, XSS, and common vulnerabilities. Read more here
. It has known security vulnerabilities. Please see list here
Little built-in protection. Must be handled by developers themselves or by using 3rd party extensions.
Ships with internally developed Kajiki templating engine, but supports multiple templating engine including Genshi
Built-in support. Read more here
TurboGears relies on ToscaWidgets2
for building and validating forms.
Ships with repoze.who which is an authentication and identity framework for WSGI applications. Read more here
If you found this useful, please help us grow by sharing this article with your followers using the sharing icons. Every share or call out will help. Thank you.