I'll be spending the next two years working on a event-driven python
application server. As part of this work, I'll be investigating
asynchronous database calls. I'll definitely report as I make progress
in that arena. I'm envisioning a patch to the ORM that allows writes
to be processed in the bac
Yeah - we're stuck with CentOS into the foreseeable future. Manually
compiling Python to a different prefix, and then recompiling mod_wsgi
and other modules against this version is really not an option at this
point. If Django 1.3 deprecated support for Python 2.4, then we would
be forced to remain
o now). Cheers!
-Mark
On Jul 31, 11:27 am, Jacob Kaplan-Moss wrote:
> On Sat, Jul 31, 2010 at 9:04 AM, tiemonster wrote:
> > I've been doing lots of research with Django on GAE, and am actually
> > using it in production. If you're interesting in this particular
> >
So anyways...
Google App Engine is a special case. It is not nearly as robust a
database solution as something like CouchDB or MongoDB - but then
again it was never meant to be. The direction from the beginning was
on scaling, even if it meant dropping features. The BigTable ORM lacks
many of the
Is there a reason that the default ordering on the User model is by
pk? Would it be a reasonable request to ask that the default ordering
for this model be username? I have several models that have a m2m to
the User model, and it's very hard to find someone to add using the
admin when the users are
One of the main advantages of Django over other web frameworks is
twofold:
1. Almost anything can be overridden with a custom backend (auth, e-
mail, context processors, middleware, etc.)
2. Custom backends can be plugged in side-by-side with "stock"
backends
What functionality do you feel is hol
