#29403: Make PyLibMCCache backend handle TooBig exception from pylibmc
-------------------------------------+------------------------------------
Reporter: SKisContent | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 1.11
Severity: Normal | Resolution:
Keywords: memcached, TooBig | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by Flavio Curella):
I'm not convinced we should fail silently. I understand that some versions
o memcached will, but I'd rather be warn the user that something went
wrong instead of being consistent.
If we know something went wrong we should tell the user. I'd recommend
raising a more descriptive exception, possibly using `raise ... from ...`.
--
Ticket URL: <https://code.djangoproject.com/ticket/29403#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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.35ff19f5cebfd8609b974b2027a75b12%40djangoproject.com.
