views:

781

answers:

4

I came across 2 different modules for porting django to appengine.

http://code.google.com/p/app-engine-patch/

http://code.google.com/p/google-app-engine-django/

Both seem to be compatible with django 1.0,

The featured download of the latter is in Aug 08, whereas the former is Feb 09.

What are the relative merits.

What if I dont use the database at all, would it matter.

A: 

Well, I got it myself. I used python 2.6, and it seem problmatic for app-engine. Starting with python2.5 solved it. See here:

+1  A: 

It's a bit late to answer, but the problem I've had so far with app-engine-patch is that, while it's a generally feature-complete port of Django 1.0, it discards Django models in favor of AppEngine's db.Model.

It's understandable, given the differences between the two, but it can require quite a bit of effort to port, depending on how involved your models (and usage of those models; this means you lose the Django query syntax as well).

esm
A: 

App Engine Patch is the right way to go.

Lakshman Prasad
+2  A: 

At the moment, the App Engine Patch is outdated.

Djangoappengine and Django-Nonrel provide "Native Django on App Engine": http://www.allbuttonspressed.com/blog/django/2010/01/Native-Django-on-App-Engine

d3f3nd3r
There is an updated post here: http://www.allbuttonspressed.com/projects/djangoappengine
znq