简体繁体 English

app-engine-patch已经死了。现在，在Google App Engine上使用Django的最佳方式是什么？

[英]app-engine-patch is dead. Now what is the best way to use Django on Google App Engine?

原文 2010-02-17 18:38:13 3 2 python/ django/ google-app-engine/ app-engine-patch

The app-engine-patch authors have officially marked this wonderful project as dead on their website. app-engine-patch作者正式将这个精彩的项目标记为在他们的网站上死亡。 Over the last year a lot of people have asked what the best way to run Django on Google App Engine was, and time after time people have pointed to app-engine-patch being the way to go. 在过去的一年中，很多人都问过在Google App Engine上运行Django的最佳方式是什么，并且人们一次又一次指出app-engine-patch是最佳选择。 Now that this project is dead, I would love to revisit this discussion and see what you all would recommend. 既然这个项目已经死了，我很乐意重温这个讨论，看看你们都会推荐什么。

The old app-engine-patch website refers to a different project called djangoappengine that they are working on. 旧的app-engine-patch网站引用了一个名为djangoappengine的不同项目。 It focuses on using Native Django on App Engine but by doing so appears to limit your ability to use all of App Engine's features (such as its built in User model). 它侧重于在App Engine上使用Native Django，但这样做似乎限制了您使用App Engine所有功能的能力（例如其内置的用户模型）。 What do you all think about this as a replacement solution? 作为替代解决方案，您对此有何看法？

Does the Google App Engine Helper For Django project now look more inviting now that app-engine-patch has died? 现在，app-engine-patch已经死亡，那么Django项目的Google App Engine Helper现在看起来更具吸引力吗？

Or is app-engine-patch still so great that you would recommend still using it despite it being dead? 或者app-engine-patch仍然是如此之大，以至于尽管它已经死了你仍会建议仍然使用它？

I currently have a project in its middle stages relying on app-engine-patch and have loved using it so far, but am scared to continue using a project that is dead. 我目前有一个项目处于中间阶段，依赖于app-engine-patch，并且喜欢使用它到目前为止，但我害怕继续使用已经死亡的项目。 I would really appreciate any comments you have about what you think the best long term solution is now. 如果您对现在最好的长期解决方案有何看法，我将不胜感激。 Thanks! 谢谢！

2 个解决方案

App engine patch is probably a safer bet for a given moment. 对于特定时刻，应用引擎补丁可能是更安全的选择。 Though not actively supported at the moment, it's still great, as it's been tested more thoroughly. 虽然目前尚未得到积极支持，但它仍然很棒，因为它已经过更彻底的测试。 If you're ready to take some risks - go and give the new djangoappengine+django-nonrel (native django support for non relational databases, primarily google datastore yest) option a try. 如果您已准备好承担一些风险 - 请尝试使用新的djangoappengine + django-nonrel（非关系数据库的本机django支持，主要是google datastore）。 That is the option we'll all use in a little while, so probably it's worth to try it out and not to look back. 这是我们将在一段时间内使用的选项，所以可能值得尝试一下而不是回头看。 For instance, app engine patch only supports ~300 entities in the admin (ie doesn't take advantage of the 1.3.1 functionality), while with the djangoappengine+django-nonrel that is not an issues anymore. 例如，app引擎补丁仅支持管理员中的~300个实体（即不利用1.3.1功能），而djangoappengine + django-nonrel不再是问题。 www.allbuttonspressed.com, a site of the guys behind app-engine-patch, is all built this new way, you can grab the source code of the site's skeleton @ http://bitbucket.org/wkornewald/allbuttonspressed/ . www.allbuttonspressed.com，一个app-engine-patch背后的人的网站，都是以这种新方式构建的，你可以抓住网站骨架的源代码@ http://bitbucket.org/wkornewald/allbuttonspressed/ 。