应用程序引擎补丁已死。现在在 Google App Engine 上使用 Django 的最佳方式是什么？
app-engine-patch 作者已在其网站上正式将这个精彩的项目标记为死亡 。 去年，很多人问在 Google App Engine 上运行 Django 的最佳方式是什么，人们一次又一次指出 app-engine-patch 是最佳选择。现在这个项目已经结束了，我很想重新审视这个讨论，看看你们会推荐什么。
旧的 app-engine-patch 网站引用了他们正在开发的一个名为 djangoappengine 的不同项目。它专注于在 App Engine 上使用 Native Django，但这样做似乎会限制您使用 App Engine 的所有功能（例如其内置的用户模型）的能力。大家觉得这个替代解决方案怎么样？
Google App Engine Helper For Django 项目现在看起来是否更有吸引力-引擎补丁已经死了吗？
或者 app-engine-patch 仍然如此出色，以至于您建议尽管它已经死了，但仍然使用它？
我目前有一个项目处于中期阶段，依赖于 app-engine-patch，到目前为止我很喜欢使用它，但我害怕继续使用一个已经死了的项目。我非常感谢您对您认为现在最好的长期解决方案提出的任何意见。谢谢！
The app-engine-patch authors have officially marked this wonderful project as dead on their website. 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. 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. 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). 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?
Or is app-engine-patch still so great that you would recommend still using it despite it being dead?
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. I would really appreciate any comments you have about what you think the best long term solution is now. Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看来您可以使用 use_library 导入它...
http:// /code.google.com/appengine/docs/python/tools/libraries.html
It looks like you can just import it using use_library...
http://code.google.com/appengine/docs/python/tools/libraries.html
在特定时刻，应用程序引擎补丁可能是更安全的选择。尽管目前没有得到积极支持，但它仍然很棒，因为它已经过更彻底的测试。如果您准备好承担一些风险，请尝试一下新的 djangoappengine+django-nonrel （原生 django 支持非关系数据库，主要是 google 数据存储）选项。这是我们稍后都会使用的选项，因此可能值得尝试一下，而不是回头看。例如，应用程序引擎补丁仅支持管理中的约 300 个实体（即不利用 1.3.1 功能），而使用 djangoappengine+django-nonrel 则不再是问题。 www.allbuttonspressed.com 是 app-engine-patch 背后的人的网站，都是以这种新方式构建的，您可以获取该网站骨架的源代码 @ http://bitbucket.org/wkornewald/allbuttonspressed/。
祝你好运！
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. 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 (i.e. doesn't take advantage of the 1.3.1 functionality), while with the djangoappengine+django-nonrel that is not an issues anymore. 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/.
good luck!