Hi folks --
Yup, it's that time again!
For the tl;dr-ers, here's the short version:
* We're aiming to release Django 1.2 on March 9th, 2010.
* We'll begin voting on features for 1.2 very soon (today or tomorrow).
* We're modifying the process slightly from last time; in particular,
we're going
On Thu, Oct 8, 2009 at 11:58 AM, Wes Winham wrote:
> This gives me a nice little summary. I know that there were more foo's
> displayed on the page than there should have been.
I second that. The option to specify a quick message explaining what
the failure means, for anyone who didn't write th
I haven't looked at the proposed patch, but I'd like very much to be
able to add a ``msg`` argument to assertContains and assertRedirects
at least. The point of the msg argument in normal asserts is to give
the person running the tests a quick, high-level indication of what
went wrong or what was
On Thu, Oct 8, 2009 at 5:52 PM, Simon Willison wrote:
>
> On Oct 6, 1:25 pm, Russell Keith-Magee wrote:
>> I think we need something else. In particular, I think we need to
>> address the problem at a slightly deeper level - we need to
>> acknowledge that we don't differentiate between applicati
On Thu, Oct 8, 2009 at 5:52 AM, Simon Willison wrote:
> If we were to ship default templates, simply using {% extends base %}
> and providing an argument to the generic views that allows the user to
> specify their own base template would be enough to ensure easy
> integration with a custom desig
Hello!
I just joined Snapixel and wanted to invite you to use this
coupon.
Get unlimited photo storage here!
http://snapixel.com/coupon/freepro
Cheers.
On Oct 6, 1:25 pm, Russell Keith-Magee wrote:
> I think we need something else. In particular, I think we need to
> address the problem at a slightly deeper level - we need to
> acknowledge that we don't differentiate between application tests and
> integration tests within Django's test framewor
