There is not much love in the Django community towards web2py (to put it lightly), but if you are interested in Django on GAE it might be interesting to give we

There is not much love in the Django community towards web2py (to put it lightly), but if you are interested in Django on GAE it might be interesting to give web2py (for which GAE is a native backend) a look. The main complaints against web2py are that it is "un pythonic" because it automatically imports some things for you (from Jacob Moss Kaplan / django), and that it re-executes scripts leading to some unavoidable memory leaks in some (arguably, non-idiomatic, easy to avoid and extremely rare) situations (from Armin Ronacher / flask). I hope I have properly summarized and not misrepresented the core arguments - apologies in advance if I did. Having used both django and web2py for commercial uses, and helping newbies on the web2py list, I would say that these complaints have no practical significance. In my opinion, web2py is simpler and easier to use; and if you need GAE support, it's there.