You make a good point. I am not a Python programmer but I have tried a few AppEngine tiny experiments with Django and webapp. webapp was clearly designed for the platform. Similar case for Java: JDO or JPA never seemed like a good fit to the data store, but Objectify seems crafted to add a nice but thin layer on top of the low level APIs.
I like some of the basic infrastructure that Django gives me, so I make use of `use_library()` Django 1.1 on App Engine. It's not "full" Django but I find it more palatable than WebApp and the parts of Django that fit GAE fit it well. Models, etc should be done directly on top of the GAE APIs, in my opinion.
I think Guido's rietveld sample app is a good place to start if you're new to App Engine and want to use (the useful bits of) mainline Django.
Yes, you still have to adapt to the AppEngine way of doing things. But the adaptation is much simpler ... and I completely dislike the way webapp does a lot of things judging from the examples Google provides. I like my world nice and full of free-floating functions. Wrapping things into nearly meaningless objects hurts my brain.
Since the included version is so bad, people try to get django-app-engine-patch or django-norel working. Those also suck.
There's a mindset that if Django runs, I can keep doing things the Django way.
Nope. Abandon your old frameworks. If you're going to use App Engine, you have to embrace its distributed, scalable way of doing things. Use something made for App Engine like webapp or tipfy.
Yeah, there are problems with App Engine. It has downtime and things slow down. So does every other hosting platform.
App Engine is getting better all the time. I've been working with it for about 6 months, and nearly every month there is a new release with great new features that make developing apps for the platform better. The new 1.4 release has tons of great features that will make working with App Engine easier, like reserved instances and warming requests.