Marking as a feature request.

Dan Sanderson has put together an article detailing how to get Django 1.0 running on
App Engine without hitting either the 1,000 file limit or the 1MB limit. It may be
useful in running 1.0 before we officially support it:
http://code.google.com/appengine/articles/django10_zipimport.html

I'm using app engine patch on every project. 

Keeping up to date with django versions would be great for Python in general.  maybe
a way to explicitly choose the version in settings.py or the main handler?

it be easier to put django somethere in non path, and give us a configurable app.yaml
instruction or some small piece of code to patch in.. would also save a lot of space
on the servers.. reducing all those copies of the same zip to ONE!

The above article listed by Deo is good, but I have written a more in depth tutorial
that works with GAE 1.1.9 using Django 1.0.2. Since I am new to Python, App Engine
and Django, any comments or improvements to the tutorial would be appreciated!

You can find the how-to here:
http://sankasaurus.blogspot.com/2009/02/django-and-google-app-engine-tutorial.html

Or, better yet, use app engine patch: http://code.google.com/p/app-engine-patch/

 Issue 1166  has been merged into this issue.

Now that Django 1.1 has entered beta, please target it instead of 1.0.

Django 1.1. is a must

Django 1.1 will come in a future release, and not before it's out of beta.

This is killing the response times of my low-traffic app, because apps are
aggressively flushed from memory, after 2-3 seconds, my app has to cold-start again
and zipimport django 1.0. This would not happen if supported by the app engine
directly. Until then, I am contemplating backporting my app to 0.96.

Django 1.1 native support is highly needed.

This was fixed in 1.2.3: http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

It's indeed fixed, though not yet documented.

To use:

1. Install Django 1.0 into the Python version you're using with the SDK (usually the
system Python).

2. In your app:
from google.appengine.dist import use_library
use_library('django', '1.0')

You no longer need to copy Django 1.0 into your app, nor do you need to mess with
sys.modules, sys.path and zipfiles.  (Though those instructions still apply if you
want to use Django 1.1 -- we'll start supporting that once it's out of beta.)

Note, Django 0.96 is still the default, and can also explicitly be requested by using
use_library('django', '0.96') -- in API v2, we'll probably change things so you
*have* to specify a Django version before you can use it.

We're contemplating the support of other open source packages as well (as long as
they don't contain C code).

Any chance for http://code.google.com/p/app-engine-patch/ ?

Shouldn't http://code.google.com/appengine/articles/django.html be updated to refer to Django 1.0?

This breaks GAE admin support if the admin (or any webapp because webapp imports django) is viewed before a 
Django handler that sets use_library(...) with a: 

google.appengine.dist._library.UnacceptableVersionError 

See issue #1758.

Unfortunately, that is indeed a current limitation.  The short-term work-around is to
hit / before hitting /_ah/admin after (re)starting the dev appserver.  Note that the
dev appserver effectively restarts whenever you edit any of the source code (.py
files) too.

As a long-term solution, I am not sure yet, but there has to be one.

A possible fix would be to allow us to override (or disable) the admin url mapping at /_ah/ and replace it with our 
own handler script that does something like this:

from google.appengine.dist import use_library
use_library('django', '1.0')

from google.appengine.ext.admin import main as admin_main

def main():
	admin_main()

Right now I have to map another url to do this, which seems wasteful.

The long-term solution might be along the lines suggested by prosarath: put it in the
app.yaml. If all we need is something that gets read whenever the server starts up,
and says which version of django we want then this sounds like the perfect solution.

Django 1.1 is out of beta, when can we see it.

I started the process for including Django. There is a planned upcoming AppEngine
release that is too far through QA to add something like this; I expect Django 1.1
support to go into the release after that.

You can also use app-engine-patch 1.1RC which comes with the latest Django 1.1 stable 
release:
http://code.google.com/p/app-engine-patch/

i'm trying to use_library('django', '1.1'), but am getting "You haven't set the DATABASE_ENGINE setting yet." when 
leaving DATABASE_ENGINE = '' in my settings.py

what am i supposed to set this to for developement? 

Django needs to modified to run on appengine. Try

http%3A%2F%2Fcode.google.com%2Fp%2Fapp-engine-
patch%2F&resnum=1&sa=X&usg=AFQjCNEtNckEQGeYXBJc7Q7rug4Q2fm2PA

or any of the other products from a google "django apengine". 

This question can probably be better answered in a google groups form. 

I'm not sure, but I think you can leave it unset -- that's what I do in Rietveld (check out 
http://code.google.com/p/rietveld/source/browse/trunk/settings.py ).

django 1.0 claimed be supported, still no django naturalday (1.0 filter) or just 
undocumented

@niklasro: did you put the use_library('django', '1.0') incantation in your code at the 
right place?

will give it 2nd try now kindly informed it can, tried it once and failed more miserably than anyone, naturalday 
seems natural view worth enabling, didn't see it reading the filter gae part which lead thought to naturalday 
was downprioritized

I am just using django templating system via as included by the fault in Google App
Engine:
  import google.appengine.ext.webapp.template

It seems this uses .96 syntax. Is there a simple way of just using the 1.0 (or 1.1)
Django templating system together with webapp?

Please ask further questions on the group.