On Feb 7, 2:14 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> I've reopenedhttp://code.djangoproject.com/ticket/5124.
> 'contains_nontext' must be an instance attribute, not a class
> attribute in 'NodeList'. There is a patch attached.
Arrggh... my humble apologies... been following the template code,
On Feb 7, 2:26 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> BTW, do I understand this correctly...
> {# comment #} is alright, but {% comment %} ... {% endcomment %} is
> not? I don't see anything in the code that would allow block
> comments. Would be nice if it did...
This could be implemented ea
BTW, do I understand this correctly...
{# comment #} is alright, but {% comment %} ... {% endcomment %} is
not? I don't see anything in the code that would allow block
comments. Would be nice if it did...
Wayne
--~--~-~--~~~---~--~~
You received this message be
I've reopened http://code.djangoproject.com/ticket/5124.
'contains_nontext' must be an instance attribute, not a class
attribute in 'NodeList'. There is a patch attached.
Wayne
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
Thanks, I try to do my best and five mistakes in the same sentence is
not that bad ;)
Cheers,
David
Le 7 févr. 08 à 15:31, J. Cliff Dyer a écrit :
>
> I made a couple of minor grammatical changes for clarity, but your
> english was pretty good, David.
>
> Cheers,
> Cliff
>
> On Thu, 2008-02-0
I made a couple of minor grammatical changes for clarity, but your
english was pretty good, David.
Cheers,
Cliff
On Thu, 2008-02-07 at 15:06 +0100, David Larlet wrote:
>
> Le 6 f�vr. 08 � 21:01, SmileyChris a �crit :
>
> >
> > On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> > wro
Le 6 févr. 08 à 21:01, SmileyChris a écrit :
>
> On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
>> It already results in a broken site, we're now just being a lot
>> clearer
>> about that.
>
> Actually, it only resulted previously in a broken site if the extended
> template
On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> It already results in a broken site, we're now just being a lot clearer
> about that.
Actually, it only resulted previously in a broken site if the extended
template was being used in more than one depth of inheritance.
>
> Still
On Wed, 2008-02-06 at 09:26 +0100, David Larlet wrote:
>
> Le 5 févr. 08 à 22:05, Malcolm Tredinnick a écrit :
>
> >
> >
> > On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote:
> >> Hello,
> >>
> >> I'd just updated my local version of django and it raises errors due
> >> to 7084 changeset (
Le 5 févr. 08 à 22:05, Malcolm Tredinnick a écrit :
>
>
> On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote:
>> Hello,
>>
>> I'd just updated my local version of django and it raises errors due
>> to 7084 changeset (extends should be the first tag). I put all my
>> extends tags above all my
On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote:
> Hello,
>
> I'd just updated my local version of django and it raises errors due
> to 7084 changeset (extends should be the first tag). I put all my
> extends tags above all my load tags in every templates and I realize
> that it rais
David Larlet said the following:
> I'd just updated my local version of django and it raises errors due
> to 7084 changeset (extends should be the first tag). I put all my
> extends tags above all my load tags in every templates and I realize
> that it raises errors for comment tags too... I
Hello,
I'd just updated my local version of django and it raises errors due
to 7084 changeset (extends should be the first tag). I put all my
extends tags above all my load tags in every templates and I realize
that it raises errors for comment tags too... I used to keep svn infos
at the
13 matches
Mail list logo
