App-engine-patch is dead. Now, what is the best way to use Django in the Google App Engine?

The authors of app-engine-patch officially marked this wonderful project as dead on their website. Over the past year, many people have asked what the best way to run Django on the Google App Engine was, and from time to time, people have pointed out that a motor patch application is the way to go. Now that this project is dead, I would like to return to this discussion and see what you recommend.

The old app-engine-patch website belongs to another djangoappengine project they are working on. It focuses on the use of Native Django in the App Engine, but apparently this limits your ability to use all the features of the App Engine (for example, the built-in User model). What do you all think of this as a substitute solution?

Does the Google App Engine Helper project for Django now create a more attractive moment when the app-engine-patch patch has died?

Or is the patch engine app still so great that you would recommend using it even though it's dead?

I currently have a mid-range project based on the patch-patch application, and I really like to use it so far, but I'm afraid to continue to use the dead project. I would really appreciate any of your comments on what you think of the best long-term solution. Thank!

+5
source share
2 answers

, , . , - , . - djangoappengine + django-nonrel ( django , google datastore yest). , , , , . , ~ 300 (.. 1.3.1), djangoappengine + django-, . www.allbuttonspressed.com, -engine-patch, , @http://bitbucket.org/wkornewald/allbuttonspressed/.

!

+4

All Articles