On Fri, Sep 5, 2008 at 2:34 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Does the error message pretty easily let you figure out what's wrong?
>
A problem I've seen with infinite recursion is that while it may manifest
itself pretty clearly on one platform, the same root problem may show
entirely different symptoms on another platform. See #8313, #8314, and
#8315, all caused by the same error, manifested as Python interpreter
crashes, reported infinite recursion, and reported database error. The
first case is particularly hard to debug, so I'd be inclined to try to
prevent the infinite recursion, assuming detecting the user-level problem
that causes it is not too difficult.
Karen
> On Aug 31, 1:38 pm, Martin Ostrovsky <[EMAIL PROTECTED]>
> wrote:
> > Now I'm not sure if this is a bug worth squashing or more a case of if
> > you're dumb, you deserve what you get but ... I erroneously extended a
> > template with itself (it was a typo, that's how I stumbled upon it).
> > So say you have a template called home.html and had the following in
> > it:
> >
> > {% extends 'home.html' %}
> >
> > This causes infinite recursion as
> > django.template.loader_tag.ExtendsNode.get_parent is repeatedly called
> > until Python says that's enough, and crashes. This also happens if
> > template A extends template B and template B extends template A.
> >
> > Again, these two scenarios make no sense at all and don't represent
> > logical use cases. I'm just wondering if it's something we want to
> > address?
> >
> > - Martin
> >
>
--~--~---------~--~----~------------~-------~--~----~
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 unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
