#8420: Inconsistent use of template_name in generic views
------------------------------------+---------------------------------------
Reporter: benjixx | Owner: nobody
Status: closed | Milestone: 1.0
Component: Generic views | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
Not worth it. It would break every piece of code using that template for
no real reason. You don't just switch on generic view for another with no
other changes, so changing this at the time isn't a real hardship. Yes, it
might be nice if we were starting from scratch, but introducing random
backwards-incompatible changes that don't really improve functionality
isn't a good idea at the moment.
--
Ticket URL: <http://code.djangoproject.com/ticket/8420#comment:1>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
