#29403: Make PyLibMCCache backend handle TooBig exception from pylibmc
-------------------------------------+-------------------------------------
Reporter: SKisContent | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: closed
Component: Core (Cache system) | Version: 1.11
Severity: Normal | Resolution: needsinfo
Keywords: memcached, TooBig | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: assigned => closed
* type: Bug => Cleanup/optimization
* resolution: => needsinfo
Comment:
Like [https://code.djangoproject.com/ticket/29403#comment:3 Flavio
Curella] and
[https://github.com/django/django/pull/9811#issuecomment-387895386 Ed
Morley], I'm not convinced that we should catch this exception, it was
shortly discussed in
[https://code.djangoproject.com/ticket/19914#comment:4 #19914]. See also
arguments in [https://code.djangoproject.com/ticket/28342#comment:8
#28342] (this is not a duplicate but is related). The main question is:
should we force consistency between these two backends? IMO it's better to
respect their different policies of handling errors.
I think we should go back to the DevelopersMailingList and reach a
consensus to move it forward.
--
Ticket URL: <https://code.djangoproject.com/ticket/29403#comment:5>
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/069.bc9049a03b48df89dbe16cbbb717bdaf%40djangoproject.com.
