#15303: Functions passed as kwargs to View.as_view() should be bound
-----------------------------------------+----------------------------------
Reporter: gg | Owner: nobody
Status: new | Milestone: 1.3
Component: Documentation | Version: SVN
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_docs: => 0
* component: Generic views => Documentation
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
As discussed on IRC: I'm not sure I see why we should make the
implementation of the generic view base class a whole lot more complicated
in order to allow users to avoid creating a subclass. Passing arguments in
to as_view() is a convenience for the really simple cases -- it isn't
intended as a way to avoid ever needed to create a View subclass.
However, I can see how the phrasing about "overriding pattern" could lead
to this expectation, so that should be cleaned up.
--
Ticket URL: <http://code.djangoproject.com/ticket/15303#comment:1>
Django <http://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.
