#17249: cache.set() returns None, even in the case of failure
-------------------------------------+-------------------------------------
Reporter: russellneufeld@… | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage:
Has patch: 1 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ptone):
Replying to [comment:2 anonymous]:
> Validating success in the case of memcache is a no-op. The result is
already in the python code. I just added the word "return", so there's no
performance impact to this change.
You're missing the point that code using cache is backend agnostic, so
what might be no-op in memcache isn't sufficient alone to consider a
change to the general cache API
--
Ticket URL: <https://code.djangoproject.com/ticket/17249#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
