#25600: Template `if` tag behavior change with 1.8, OneToOneField,
RelatedObjectDoesNotExist is True?
---------------------------------+------------------------------------
Reporter: syphar | Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by timgraham):
The `RelatedObjectDoesNotExist` exception is a subclass of
`AttributeError` -- that's why it's hitting that logic added in the commit
noted in the previous comment. 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 think the usage of `string_if_invalid` is somewhat
unreliable/unpredictable anyway and therefore discouraged but I'm not too
sure as I haven't used it myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/25600#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.bac0cf85d66162214b98986a4a1e4314%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
