#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: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by timgraham):
* severity: Release blocker => Normal
Comment:
Per [https://groups.google.com/d/topic/django-
developers/BLW5fCTDYHA/discussion discussion on django-developers],
demoting from a release blocker since `string_if_invalid` is only intended
for debugging. Inconsistencies in how the `{% if %}` tag silences
exceptions (#17664) may be related.
--
Ticket URL: <https://code.djangoproject.com/ticket/25600#comment:7>
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.c3ec23dd61366b70856ddff707940f8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
