It's a fork of the django project made specifically for no-sql databases like Google App Engine and MongoDB. The main benefit of it is that you get to piggy-back on all the cool stuff coming out of the django project, while also running on GAE's scalable architecture. Another benefit is that with djangoappengine, you can more easily move off of App Engine than if you used their API directly (although that is probably easier said than done).
There were rumors that Django would merge the changes into the mainline Django project, but it has not happened yet (as of May 2014).
I wrote GAEStarterKit, which aims to get you up to speed as quickly as possible. It's in a similar vain to projects like GAE-Boilerplate or gae-init, but a few key differences:
First and most obvious, I used UIKit over HTML5 Boilerplate. Boilerplate is a great choice, and obviously is popularity comes with perks, but for the purposes of getting started quickly, I find uikit a bit more "complete."
I put a lot of work into making sure the user login/registration system is as well-thought-out as possible. Users can have multiple email addresses, multiple authentication methods, and be associated with multiple tenants, if applicable. The social login side for non-Google users is done via Authomatic, which is a great project and very well-supported.
Although it's a little rough around the edges, I did something pretty similar to Django's GenericViews, but in Flask and with GAE Models. I used WTForms integration for that, so it all works pretty well out of the box. It's certainly not perfect, but it's pretty good.
I really took seriously the idea of not repeating myself. For example in gae-init, you'll find a lot of CRUD code. For the admin side, you can add a model to your admin GUI in GAEStarterKit with one import, and one function all.
which was written specifically for GAE. I love Django in general, but not for gae, I felt using django-nonrel still requires too many caveats that it is not worth it.
发布评论
评论（7）
更新：这个答案现在已经过时了。
对我来说，选择是 djangoappengine。
它是 django 项目的一个分支，专为 Google App Engine 和 MongoDB 等非 SQL 数据库而设计。它的主要好处是您可以利用 django 项目中所有很酷的东西，同时还可以在 GAE 的可扩展架构上运行。另一个好处是，使用 djangoappengine，您可以比直接使用 App Engine 更轻松地脱离 App Engine（尽管这可能说起来容易做起来难）。
有传言称 Django 会将这些更改合并到主线 Django 项目中，但尚未发生（截至 2014 年 5 月）。
一些相关链接：
UPDATE: This answer is now out of date.
For me the choice is djangoappengine.
It's a fork of the django project made specifically for no-sql databases like Google App Engine and MongoDB. The main benefit of it is that you get to piggy-back on all the cool stuff coming out of the django project, while also running on GAE's scalable architecture. Another benefit is that with djangoappengine, you can more easily move off of App Engine than if you used their API directly (although that is probably easier said than done).
There were rumors that Django would merge the changes into the mainline Django project, but it has not happened yet (as of May 2014).
Some relevant links:
我个人很喜欢使用以下模板在 App Engine 上使用 Flask：
https://github.com/kamalgill/flask-appengine-template
代码组织良好这个模板非常好，它包含许多不错的开发功能，例如分析和应用程序统计信息。
I personally have enjoyed using Flask on App Engine using this template:
https://github.com/kamalgill/flask-appengine-template
The code is organized pretty well in this template and it includes many of the nice development features like profiling and app stats.
如果你想构建大型应用程序并需要更灵活的框架，那么你可以看看
Pyramid Python框架
以前它被称为
Pylons。有很多优秀的公司使用这个框架。您可以在其网站上找到有关将其部署到 appengine 的过程的说明： http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/deployment/gae_buildout.html 该过程使用构建还包括本地测试环境。
If you want to build large scale application and need a more flexible framework, then you can take a look at
Pyramid Python Framework
Previously it was called
Pylons. There are lot of good companies using this framework.You can find instructions for the process of deploying it to appengine on their website: http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/deployment/gae_buildout.html The process uses buildout and also includes a local testing environment.
我对这个样板非常满意：
https://github.com/coto/gae-boilerplate
看看它的功能和特点，很齐全！
I'm very happy with this boilerplate:
https://github.com/coto/gae-boilerplate
Take a look at its functions and features, it's very complete!
（请注意，此答案已过时，不再有效。）
阅读 Tom Willis 对问题的评论以及 这个问题的接受的答案我注意到webapp/webapp2看起来很有希望。
(Note that this answer is old and no longer valid.)
After reading Tom Willis' comment on the question and also this SO question's accepted answer I noticed that webapp/webapp2 looks promising.
我编写了 GAEStarterKit，旨在让您尽快上手。它与 GAE-Boilerplate 或 gae-init 等项目类似，但有一些关键区别：
可能值得考虑。
I wrote GAEStarterKit, which aims to get you up to speed as quickly as possible. It's in a similar vain to projects like GAE-Boilerplate or gae-init, but a few key differences:
Might be worth considering.
我很喜欢
http://ferris-framework.appspot.com/
专门为 GAE 编写的 。总的来说，我喜欢 Django，但不喜欢 gae，我觉得使用 django-nonrel 仍然需要太多警告，因此不值得。
I am enjoying
http://ferris-framework.appspot.com/
which was written specifically for GAE. I love Django in general, but not for gae, I felt using django-nonrel still requires too many caveats that it is not worth it.