Do I need either to make Django easier to use on GAE? Anyone had good or bad experience of either or any equivalent? Is there much difference between these? Which is easier to use?
Regards
Geoff
views:
953answers:
4
A:
Use Django patch if you already have django application that you know that you want to use. Remember that GAE comes with its own API/applications.
phmr
2009-08-06 08:13:41
+11
A:
I am assuming you want to run django on app engine (otherwise using appengine API directly is the best solution).
Altho' Google App engine supports django 1.0 out of the box, django admin, auth doesn't work on it, as they are dependent on the models.
Appengine patch patches django to make the admin work even on the Bigtable API.
Appengine patch also often makes sure to work on the latest release of django.
So, again, "You should use App engine patch"
Lakshman Prasad
2009-08-06 09:54:16
According to the app engine patch site, "app-engine-patch is no longer being updated " and "Join the Django nonrel project and follow the Django nonrel blog (which is written with Django nonrel) if you want to use Django's ORM on App Engine and other NoSQL / non-relational databases. Django nonrel will allow to run your code on App Engine, MongoDB, SimpleDB, and SQL without any modifications..."
Chip Tol
2010-03-28 21:14:31
btol45, Thanks. It is True. However this was answered in Aug 2009, which is like 8 months ago :)
Lakshman Prasad
2010-03-29 08:50:49
+2
A:
I think it depends on what exactly you want to develop.
You should use app-engine-patch if you need the Django Admin interface, otherwise google-app-engine-django should be enough.
Paolo Moretti
2009-08-06 19:43:43
+4
A:
Google App Engine Patch seems to have died sometime around August 2009.
http://code.google.com/p/app-engine-patch/issues/detail?id=253
rickmode
2010-01-27 01:09:51
It supports Django 1.1 and the replacement (http://bitbucket.org/wkornewald/django-nonrel/) is not ready yet, so it is still a good option.
cope360
2010-02-14 04:41:49