#29893: Unexpected behavior of DetailView on a model defining __len__()
returning
False
-------------------------------+--------------------------------------
Reporter: Max | Owner: Max
Type: Bug | Status: closed
Component: Generic views | Version: 2.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Tim Graham):
* status: assigned => closed
* resolution: => wontfix
Comment:
I agree with Simon that trying to adapt the Django ecosystem to this
convention is likely an unreasonable burden. You can write to the
DevelopersMailingList if you want to try to convince the community
otherwise. It would certainly help your argument if you explained why you
want to define `__len__()` as such. Others may suggest a better solution
for the problem you're trying to solve.
--
Ticket URL: <https://code.djangoproject.com/ticket/29893#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.dbe2f5b0eb8fb3dbc31cb38d13f0f562%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
