#29867: Allow cache.get_or_set() to cache a None result
-------------------------------------+------------------------------------
Reporter: phill-tornroth | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 2.1
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
-------------------------------------+------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Comment:
I agree with your analysis. I read through previous related issues
(#26792, #28601) and didn't see a good reason for the current behavior. I
would question if `if default is not None:` should be there in your
proposal (i.e. why shouldn't `None` by cached?).
--
Ticket URL: <https://code.djangoproject.com/ticket/29867#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.69554de0aa01cf0f8e50b9003395d5d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
