#29867: Allow cache.get_or_set() to cache a None result
-------------------------------------+-------------------------------------
Reporter: Phill Tornroth | Owner: Ahsan
| Shafiq
Type: Bug | Status: assigned
Component: Core (Cache system) | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* needs_better_patch: 0 => 1
Comment:
I think we should move forward with
[https://github.com/django/django/pull/13671 Nick's PR] which is to handle
`None` in all affected methods. Marking as "needs improvement" because
it's still PoC.
--
Ticket URL: <https://code.djangoproject.com/ticket/29867#comment:12>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.bd1561944f844b6cac292ef12d888ae6%40djangoproject.com.
