#21065: Internally choosing how to process a template is inconsistent
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: nobody
<django@…> | Status: new
Type: | Version: master
Cleanup/optimization | Resolution:
Component: Template system | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by mjtamlyn):
* stage: Unreviewed => Accepted
Comment:
+1 to improving the consistency here. I think it's safe from a compat
point of view because the three cases should be independent of each other.
I like the idea of a proper function with public api for doing this, it
seems common for someone wishing to implement extensions or alternatives
to the API without worrying about this exact implementation.
--
Ticket URL: <https://code.djangoproject.com/ticket/21065#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/095.f324df96c6e3c37e8b24bf6f4c938e31%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
