On Sun, Nov 23, 2008 at 4:42 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
> I could not find any mention of this in the Version 1.1 features or
> roadmap. I guess it'll have to wait till next release. Could you
> please confirm?
It's a pretty small change with no real backwards-incompatibility
On Nov 9, 7:56 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> The Djangotestclient exposes theContextused to render the returned
> response, so that unit tests can inspect thatContextand verify that
> it contained what it was expected to contain. This is all well and
> good, except that there
Well I guess I'm not too familiar with how the Django process goes
from proposal to actual feature, but I was looking for something a bit
more concrete. Something that says "we're going to use this as an API,
here is how it will work, now let's get to coding".
On Nov 22, 4:13 pm, "Jacob
Hmm, now that's an interesting implementation. I'm pleased to see you've
essentially taken the same route I did in terms of detecting when to
save, which means I'm not being as silly as I first thought.
The decorator syntax is nice, and certainly something that should be
around - however, I
