The expected behavior of the {% if %} tag isn't clear to me. How do you
propose to solve the "bug"? As I noted in the ticket:
We end up checking {% if <string_if_invalid> %} which passes for a
non-empty string_if_invalid. I'm not sure we should add special handling of
RelatedObjectDoesNotExist in the template engine to restore the old
behavior (and I'm not sure how to since RelatedObjectDoesNotExist is a
dynamically generated exception based on the related descriptors).
I guess this is related to https://code.djangoproject.com/ticket/17664
which describes inconsistencies in how the if tag silences exceptions.
On Wednesday, November 11, 2015 at 4:56:03 PM UTC-5, Shai Berger wrote:
>
> On Tuesday 10 November 2015 21:32:36 Tim Graham wrote:
> > I'd appreciate some opinions on whether or not we should treat this
> issue
> > as a regression: https://code.djangoproject.com/ticket/25600
>
> Since this is essentially about the `string_if_invalid` configuration
> option,
> whose documentation carries a very clear "For debug purposes only!"
> admonition, my inclination is to treat it as a normal bug on the grounds
> that
> it should not affect any production site.
>
> It is still a bug though, I'd like to see it fixed for 1.9.
>
> Shai.
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/ec3d10ea-6f0a-4828-8d17-50a31f30e472%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
