You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Django 4.2, django.core.cache.backends.memcached.MemcachedCache has been deprecated and this library has become one of the two supported backends as well as their suggestion in the docs
While this library works basically as a drop-in replacement, we've identified one area where it behaves differently to python-memcached: exceptions such as MemcacheServerError('object too large for cache') are always raised.
As of Django 4.2,
django.core.cache.backends.memcached.MemcachedCache
has been deprecated and this library has become one of the two supported backends as well as their suggestion in the docsWhile this library works basically as a drop-in replacement, we've identified one area where it behaves differently to
python-memcached
: exceptions such asMemcacheServerError('object too large for cache')
are always raised.For comparison,
django-pylibmc
will log an error insteadIn order to align the behaviours, would you be open to a similar handling here?
pymemcache/pymemcache/client/base.py
Line 1081 in 1d565a2
We don't want to introduce a breaking change, so perhaps a new client option could work? e.g
Client(domain, raise_server_errors=True)
The text was updated successfully, but these errors were encountered: