On Dec 1, 6:08 am, Luke Plant <l.plant...@cantab.net> wrote:
> > I was with you right up until the equality comparisons (Null ==
> > Null -> False etc). As noted by Alex, it conflicts with the answer
> > given by {% ifequal %}; it also differs with Python's behavior.
>
> Yeah, I hadn't thought of that. I don't think it's a case of differing
> with Python's behaviour, as we are making a deliberate choice to
> substitute a missing variable with None (or Null or whatever). You
> could argue that Python throws a NameError in this case.
Personally, I think that "(not found)" should *not* equal "None", even
if that differs from ifequal.
But whatever, I'm not too worried either way.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
