#17381: TemplateView get method passes kwargs into context
-------------------------------+--------------------------------------
Reporter: ptone | Owner: nobody
Type: Bug | Status: new
Component: Generic views | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by russellm):
The reason for this "feature" is historical; if you look at the old-style
function based generic views, adding the kwargs to the template context
was something that the direct_to_template generic view did. The old
behavior was implemented to make it easy to port old views to the new
structures.
On a broader project level -- If something is clearly a bug, we fix it. If
this means breaking backwards compatibility, then we need to weigh the
impact of the bug against the impact of making the change without a
deprecation cycle. If there really is no way to fix a bug without
introducing a backwards incompatibility, then we'll break backwards
compatibility.
That said -- I'm not completely clear on what the 'bug' is considered to
be here. Is it that get_context_data() is being passed the wrong arguments
in a TemplateView, or that get_context_data() on a TemplateView is
constructing the wrong context data? What exactly is the bug, and what is
the consequences of that bug?
--
Ticket URL: <https://code.djangoproject.com/ticket/17381#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.