#24338: {%extends%}-ing a file-based template object is broken by deprecation
path
indirection
---------------------------------+-------------------------------------
Reporter: spectras | Owner: aaugustin
Type: Bug | Status: closed
Component: Template system | Version: 1.8alpha1
Severity: Release blocker | Resolution: fixed
Keywords: template | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"47ee7b48adbcc0dafc3404034286c5fcbcd1cea6"]:
{{{
#!CommitTicketReference repository=""
revision="47ee7b48adbcc0dafc3404034286c5fcbcd1cea6"
Fixed #24338 -- Accepted Template wrapper in {% extends %}.
Explicitly checking for django.template.Template subclasses is
preferrable to duck-typing because both the django.template.Template and
django.template.backends.django.Template have a render() method.
Thanks spectras for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24338#comment:6>
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/066.c8a847814ece2f36b0fe395f24d82c14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
