My team has adopted the convention of prepending "Sanity:" to the message of
any assertion whose purpose is to verify that things are set up correctly
for the
'main act' assertions. This helps us cut through the 'something is broken,
but it's
not here' noise when a change causes a bunch of tests t
On Fri, May 8, 2009 at 4:49 AM, Ned Batchelder wrote:
> Add the word "core" to make the first sentence, "Discussion group for
> Django core developers".
>
Good idea, but I'd take it step farther. "Core" is just ambiguous enough
outside the bubble that some people will still stop reading at the f
On Fri, Dec 26, 2008 at 9:54 AM, James Bennett wrote:
>
> On Fri, Dec 26, 2008 at 11:36 AM, Maluku
> wrote:
> > Kind of different question: Why is there no {% else %} in {% ifchanged
> > %}, I think it might be a help to some people.
>
> Because it wouldn't make any sense; the point of 'ifchanged
I'm wondering who that's going to confuse. It's very clear that the template
language
isn't Python, so I'd think it'd make the most sense to use a keyword that
makes sense
within the context of the template language. I'd think that either 'else' or
'ifnone' are the
most memorable/readable. 'default
I'd like to put in a good word for #4534 and its patch.
I know this has been discussed before, and that is *is* possible to write
view code to pass along extra data to a template to get the same effect as
ifchanged/else, but it's a lot cleaner, IMHO, to support this in templates
and to avoid clutt
On Fri, Jul 4, 2008 at 7:39 PM, Jason <[EMAIL PROTECTED]> wrote:
>
> Thanks for the replies, everyone. I double-checked my message to make
> sure it would be clear. Wonderful! And yet, I posted to the wrong
> group :( If I have a follow-up I'll post in the users forum or the
> Google App Engin
