#685: [patch] list_detail and archive_* generic views should default allow_empty
to True
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Component: Generic views
Version: SVN | Resolution:
Keywords: | Stage: Design
decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------+-----------------------------------
Changes (by mtredinnick):
* owner: anonymous => mtredinnick
* status: reopened => new
* stage: Ready for checkin => Design decision needed
Comment:
I'm not convinced this is "ready for checkin", since it breaks backwards
compatibility. Four or five commenters in a ticket does not make a vast
majority. At a minimum, I think this should wait until post-0.96 and be
part of the backwards compatible changes for 1.0 if we include it.
I'm probably +1 on including the patch, but I know there is code out there
relying on the current behaviour (I've written more than a few lines of
such code) and breaking existing sites is not cool. So I'm moving this
back to "design decision needed" in order to at least hold it over until
the forthcoming release prior to the 1.0 push. Then we can decide (along
with a bunch of other small items) whether we want to break backwards-
compat.
--
Ticket URL: <http://code.djangoproject.com/ticket/685#comment:16>
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
-~----------~----~----~----~------~----~------~--~---
