#21351: memoize function needs tests and improvements
--------------------------------------+------------------------------------
Reporter: EvilDMP | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by shai):
I don't know all the places that memoize is used, but I suspect making it
more robust will also make it slower, and for a function whose entire
reason for existence is performance, that would be a problem.
Currently, `memoize()` is undocumented, and I think we should consider
just making it explicitly private. Users don't really need it in this form
(and when they do, they should probably base it on the cache framework).
--
Ticket URL: <https://code.djangoproject.com/ticket/21351#comment:6>
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/065.6c00be3a895669388a4ccdadbee19d4f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
