#6735: Class-based generic views
------------------------------------+---------------------------------------
Reporter: jkocherhans | Owner: telenieko
Status: assigned | Milestone: 1.2
Component: Generic views | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by mmalone):
Replying to [comment:43 telenieko]:
> I think those will be deprecated in favour of the class based ones.
That's kind of dumb. Django has always supported both, why explicitly
"deprecate" one method when they're both well supported.
Also, I just took a look at Jacob's code and it looks like he's using the
`__call__` based approach, so my comments from above still apply. If you
tell someone to write a class they're going to want to store state in
instances, and I think that's going to be problematic.
--
Ticket URL: <http://code.djangoproject.com/ticket/6735#comment:44>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
