On Fri, Feb 6, 2009 at 5:51 PM, Waldemar Kornewald <[email protected]> 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 > underlying API and thus making easy migrations possible.
You won't get any disagreement here. Native support for AppEngine within Django would be a nice feature. Support for other storage backends (like CouchDB, Amazon SimpleDB, and so on) would also be nice to have. > I know that a lot of changes in the storage/query backend code need to > be done in order to support the App Engine datastore and similar > databases and I doubt that I can do the necessary API changes, but I > could at least help with implementing the App Engine backends > (sessions, cache, mail, db/storage). As a starting point, I've > documented a few high-level requirements here: > http://code.google.com/p/app-engine-patch/wiki/DjangoAppEnginePort > > Is there any roadmap towards App Engine support? Is there a formal roadmap? No. App Engine support wasn't mentioned on our v1.1 roadmap, and we don't plan beyond the next release. > Is anyone working on it, already? I'm not aware of any public projects. Reading between the lines, I suspect I know at least one person that is working on App Engine integration. However, I don't want to steal their thunder, so I'll leave it up to them to show their hand if they feel it is appropriate. > When will someone work on it and in which Django release can we expect > native support? Is 1.2 possible? The code isn't going to magically write itself, and it will be a non-trivial job. You can expect native support right after someone commits to implementing it :-) Whether this is possible for v1.2 is very much dependent on who puts in the work, and how much time they can put into the task. They will also need to convince a core developer that you are serious, and that they are capable of bringing the project to fruition. Providing an initial patch -- even if it is incomplete -- will go a long way to providing this proof. I would also note that our (that is, the Core Developers) initial reaction to non-SQL storage backends will be the same as it is for SQL database backends -- we will want to see public interest and continued support as a standalone project before we commit to integrating anything into the Django core. This policy is why we have an Oracle backend, but we don't have an MSSQL backend. There are, however, several external projects providing MSSQL integration. 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 very receptive to any suggestions on how django.db.models needs to be modified in order to support non-SQL backends -- especially if you can demonstrate that your suggestions aren't just theoretical, but are clearly required by an actual backend implementation. The goal here isn't to get AppEngine support into the core - it is to provide an interface in Django that allows you to implement an AppEngine backend (or any other backend, for that matter) as a completely standalone project. In time, this may lead to integration into the Django core, but in the interim, we would rather see a vibrant ecosystem of external plugins, rather than try and force everything into Django's trunk. > BTW, could someone please activate my "wkornewald" Trac account, so I > can move the documentation into your wiki? I just don't receive any > activation mail when registering. I tried sending to > [email protected], but that address doesn't exist. Who can I > talk to? I can mail you activation code privately. Expect an email from me shortly. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
