Updated version of Google App Engine Helper for Django available
Matt Brown
It's been several months since the last update, but I'm pleased to say
that I've just uploaded a new release of the Google App Engine Helper
for Django to the Google Code site at
http://code.google.com/p/google-app-engine-django
This release continues to increase the number of Django features that
are supported on the Google App Engine, in particular support has been
added for:
* The memcache cache backend module
* The DB and cache session backend modules
There are many other smaller changes and bugfixes also described at
http://code.google.com/p/google-app-engine-django/source/browse/trunk/CHANGES
As you'll see from the CHANGES file many of these improvements are the
result of contributions from members of the App Engine community. Thank
you very much and keep the patches coming!
This release marks the final version that will be compatible with the
stable release of Django (0.96) that is provided with the Google App
Engine SDK. Future versions of the helper will only be compatible with
the upcoming 1.0 branch of Django. Further information on how to update
your project (if desired) will be provided with the next release of the
helper.
Cheers
Matt
g-man
Caution: Change to http://localhost:8000 instead of 8080 ... this is
noted in the CHANGES file, but is not obvious from the above
invitation.
Question: How will the ModelForm change affect us? Everything seemed
OK, but should I change my import? Is there some different
functionality?
On Aug 6, 4:39 pm, Matt Brown <mattbr...@google.com> wrote:
> Hi,
>
> It's been several months since the last update, but I'm pleased to say
> that I've just uploaded a new release of the Google App Engine Helper
> This release continues to increase the number of Django features that
> are supported on the Google App Engine, in particular support has been
> added for:
> * The memcache cache backend module
> * The DB and cache session backend modules
>
Matt Brown
> OK, it installed and ran fine, but one caution and one question:
>
> Caution: Change to http://localhost:8000 instead of 8080 ... this is
> noted in the CHANGES file, but is not obvious from the above
> invitation.
Yes, I should have mentioned this more prominently, my apologies. The
helper now starts the development app server on port 8000 (the Django
default) instead of port 8080 (the App Engine devserver default).
> Question: How will the ModelForm change affect us? Everything seemed
> OK, but should I change my import? Is there some different
> functionality?
The Django model form expects Django models does not work at all with
App Engine models.
The patch replaces the Django model form class (eg.
django.forms.ModelForm) with the App Engine model form class (eg.
google.appengine.ext.db.djangoforms.ModelForm). So the following two
statements become identical:
from django.forms import ModelForm
from google.appengine.ext.db.djangoforms import ModelForm
The ModelForm class you end up with after both of them is the App Engine
model compatible class.
The benefit of this is that it reduces the amount of code that you have
to change when porting your application between "pure" Django and Django
within the App Engine environment.
As your code will already be importing ModelFrom from google.appengine
(as the Django ModelForm class has never worked with Google App Engine)
there is no need to change that unless you intend to port your
application to "pure" Django at some point in time and want to save
yourself some work.
Cheers
Matt