change the behaviour.
Have a good day,
Noam
On 7/5/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 7/5/07, Noam <[EMAIL PROTECTED]> wrote:
> >
> > The conclusion is that auto_now_add should set the date only if it is
> > None. Or, another solution: it
ot a default you
> can override. Similarly for auto_now.
Well, I didn't read it, and it was counter-intuitive to me. I spend an
hour or more on debugging, and, as I said, I don't think I'm
especially stupid. I also don't think that users should be expected to
read the ent
use I think that it would save other people hours of
annoying debugging (it would have saved me hours of annoying
debugging). I don't think that I'm especially stupid, so if it was
unintuitive to me it may be unintuitive to others.
What do y
e()
The conclusion is that auto_now_add should set the date only if it is
None. Or, another solution: it should set the date upon instance
creation, not upon saving.
Do you agree?
Noam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Thanks a lot - I switched to the unicode branch and it works very
nice! I'll report any bugs I encounter.
Noam
On 13/06/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2007-06-12 at 21:16 +, Noam wrote:
> > Hello,
> >
> > First of all, I ap
sorry if I post this in the wrong forum),
Noam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscri
;license" for more information.
(InteractiveConsole)
>>> from django.template import Template, Context
>>> t = Template('''{% block title %}Hello{% end block %}''')
Traceback (most recent call last):
File "", line 1, in
File &qu
touched at all.
(In order to make sure that all blocks of the same name really had the
same content, I added an optional argument to the parse() method which
allows it to return the list of tokens from which a block was made.)
Where should I post the diff?
Noam
(By the way, the current SVN d
ly to relax the restriction - multiple blocks with
the same name are not disallowed altogether - they are allowed, as
long as they all have the same content.
Noam
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&q
On 08/06/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On 6/8/07, Noam <[EMAIL PROTECTED]> wrote:
> > Let me improve my suggestion, so that it mostly solves James' concern
> > and can be explained in one sentence:
> >
> > -
> > Mu
of the file and then use it
a few times. It's true that you can define it in a more specific
template, but I believe that most people simply won't think of that.
And this improved suggestion has no complicated rules, and causes no
ambiguities.
better, because you gave meaning to the blocks,
but you still have to use two files when one would have sufficed and
would have stated clearly what you want. You can also say that
although it looks better, most people won't think of this solution by
themselves.
Noam
--~--~-~--~
On Jun 8, 12:02 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 6/7/07, Noam <[EMAIL PROTECTED]> wrote:
>
> > I want every page in my site to have a title. I want the title to
> > appear both in the browser title and in the page itself. A
On Jun 7, 11:17 pm, SmileyChris <[EMAIL PROTECTED]> wrote:
> Another solution is that multiple blocks with the same name inside a
> template are allowed as long as the template doesn't extend that block
> name (raise an error in that case).
>
> This way, it doesn't matter about the "meaningful" bl
ystem - {% block title %}Page Title 1{% endblock %}
{% block title %}Page Title 2{% endblock %}
{% block body %}{% endblock %}
(Of course, I could leave both blocks empty.)
What do you think about this idea?
Noam
P.S. I may be able to implement it by myself, but I wanted to get an
approval (or a di
15 matches
Mail list logo
