Yes I understand that, though that doesn't overly bother me. From the
opinion of others I think maybe its worth trying out the gae patch.

On Oct 29, 6:42 pm, Arash <[EMAIL PROTECTED]> wrote:
> Unfortunately you will not get Django's scaffolded admin interface in
> none of them
>
> On Oct 29, 1:52 pm, Adam Fisk <[EMAIL PROTECTED]> wrote:
>
> > I highly recommend app engine patch.  It's a much more active project
> > than app engine helper, and it works really well.
>
> > -Adam
>
> > On Oct 29, 10:04 am, "Dan Sanderson" <[EMAIL PROTECTED]> wrote:
>
> > > I'd recommend Django 1.0 along with the Helper or something similar.  You
> > > could use Django without the Helper if you accommodate some of the import
> > > technicalities, the Helper just makes it easier.  This article discusses
> > > using Django without the Helper (though I'm not sure if the article works
> > > out of the box with Django 
> > > 1.0):http://code.google.com/appengine/articles/django.html
>
> > > See also the article on using the Helper, and the article on using Django
> > > 1.0 via a feature called zipimport (which the Helper also supports):
> > >  http://code.google.com/appengine/articles/appengine_helper_for_django...
> > >  http://code.google.com/appengine/articles/django10_zipimport.html
>
> > > As far as compatibility goes, the runtime environment is versioned, with 
> > > the
> > > intent that changes to a given version of the runtime will remain 
> > > backwards
> > > compatible with apps that run with that version.  When a new version of 
> > > the
> > > runtime environment is released containing incompatible changes, your app
> > > will continue to use the original version until you update your app.yaml
> > > file.  I haven't tried appenginepatch, but a version of it that works with
> > > v1 of the Python runtime ought to continue to do so even when there's a 
> > > v2.
>
> > > -- Dan
>
> > > On Wed, Oct 29, 2008 at 9:24 AM, Daniel Larkin <[EMAIL PROTECTED]>wrote:
>
> > > > Hi all,
>
> > > > I'd like to use Django on GAE for a small project. Ideally I'd like to
> > > > use version 1.0 of Django rather than 0.96, and I'm aware there are
> > > > various patches and helper scripts etc to make this possible. Yet,
> > > > these approaches seem less than straight-forward (perhaps I'm
> > > > incorrect there? I haven't actually tried them) and are such patches
> > > > going to break with newer versions of GAE. After initially deciding to
> > > > use Django 1.0, I'm now considering just using the built-in 0.96
> > > > version, would this be such a bad idea for someone moving from php-
> > > > land to an elegant python MVC design pattern based solution.
>
> > > > Any comments would be greatly appreciated!
> > > > thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to