#23346: django.utils.functional.lazy picks the wrong method implementation
-------------------------------+--------------------------------------
Reporter: gavinwahl | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.6
Severity: Normal | Resolution:
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 gavinwahl):
* needs_docs: => 0
* has_patch: 0 => 1
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
https://github.com/django/django/pull/3104
> This makes the code easier to understand, in my opinion. I couldn't
figure out why methods were being pulled off of resultclasses when the
real object is available. This patch simplifies the situation and gets rid
of the `__dispatch` table completely.
--
Ticket URL: <https://code.djangoproject.com/ticket/23346#comment:1>
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.5540ea4fe78a53b98bc96fde7366d4c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
