Differences between webapp and web.py

Question

Webpy.org - Who uses web.py?

\"[web.py inspired the] web framework we use at FriendFeed [and] the webapp framework that ships with App Engine...\"

Answer 1

Differences between webapp and web.py

The primary differences (IMHO) are that:

1. The webapp framework was designed specifically for Google App Engine (GAE). The web.py framework was not designed specifically for GAE.
   • "The webapp Framework is the default tool set for building web applications [in Google App Engine] but not the only one." (Source: Developing with Google App Engine by Eugene Ciurana)
2. They use different templating languages—web.py uses its own, whereas webapp's templating language is based on Django.

Other Python frameworks for GAE

Other Python frameworks for GAE—neither of which use the Django templating language—include:

1. Flask — "A microframework for Python based on Werkzeug, Jinja 2 and good intentions."
2. tipfy — "A small but powerful framework made specifically for Google App Engine. It is a lot like webapp, but offers a bunch of features and goodies that webapp misses: i18n, sessions, own authentication, flash messages and more. Everything in a modular, lightweight way, tuned for App Engine."

Is it worth the trouble to bundle webpy when Appengine already offers webapp?

Personally, I think that it is worthwhile to use something besides webapp. However, I would lean toward Flask or tipfy.

Alex Martelli endorses tipfy in his answer to the SO question Google App Engine - Secure Cookies. The main takeaway for me from Alex's answer is that tipfy is:

1. Designed to work with GAE
2. Lightweight
3. Contains built-in functionality that you often want