Re: App Engine port

On Fri, Feb 6, 2009 at 11:51 PM, David Stenglein wrote: > > I have to ask a question here. Why is there such reticence regarding > App Engine? It would > seem to me that App Engine has been a feather in the cap for Django. A > lot of people don't know Django and at a

Re: App Engine port

On Fri, Feb 6, 2009 at 8:51 AM, David Stenglein wrote: > I have to ask a question here. Why is there such reticence regarding > App Engine? I'm curious as to what reticence you think there is; since, as Russell said, code to get a straight Django with all features

Re: App Engine port

I have to ask a question here. Why is there such reticence regarding App Engine? It would seem to me that App Engine has been a feather in the cap for Django. A lot of people don't know Django and at a previous job, I was able to say that "Google chose django" for App Engine to help validate my

Re: App Engine port

On 6 Feb., 13:10, Russell Keith-Magee wrote: > Ok - sounds like they could be some good contributions. I just wanted > to make sure you were not planning on making the Django wiki the home > of the "how to use app-engine-patch" documentation. Hmm, now that you mention

Re: App Engine port

On Fri, Feb 6, 2009 at 8:32 PM, Waldemar Kornewald wrote: > > Hi Russell, > > On 6 Feb., 11:34, Russell Keith-Magee wrote: >> I would suggest to you that the broader project of "modifying the >> django.db.models interface to be fully independent of

Re: App Engine port

Hi Russell, On 6 Feb., 11:34, Russell Keith-Magee wrote: > I would suggest to you that the broader project of "modifying the > django.db.models interface to be fully independent of SQL" is much > more likely to get core developer support. We (the Django core) will > be

Re: App Engine port

On Fri, Feb 6, 2009 at 5:51 PM, Waldemar Kornewald wrote: > > BTW, could someone please activate my "wkornewald" Trac account, so I > can move the documentation into your wiki? After I pressed send, something else occurred to me: Before you starting loading documentation

Re: App Engine port

On Fri, Feb 6, 2009 at 5:51 PM, Waldemar Kornewald wrote: > > A native Django port could provide us with a clean, more powerful, and > more actively developed API for App Engine development. Moreover, it > could provide a solution for provider lock-in by abstracting the >

App Engine port

Hi everyone, first of all, let me introduce myself. I'm the main developer behind app-engine-patch which is a port of Django to App Engine: http://code.google.com/p/app-engine-patch/ Our repository version of Django now even supports the admin interface and almost all of Django's other features,