CODEWITHSUNDEEP
djangogoogle-app-engine
user314847
user314847

Reputation: 184

Should I use google-app-engine-django or app-engine-patch or neither or something else?

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

Upvotes: 15

Views: 1375

Answers (4)

rickmode
rickmode

Reputation: 115

Google App Engine Patch seems to have died sometime around August 2009.

http://code.google.com/p/app-engine-patch/issues/detail?id=253

Upvotes: 4

Paolo Moretti
Paolo Moretti

Reputation: 55996

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.

Upvotes: 2

lprsd
lprsd

Reputation: 87155

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"

Upvotes: 11

amirouche
amirouche

Reputation: 7883

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.

Upvotes: 0

Related Questions