Upgrading from 0.4.5 to 0.4.6 breaks configurations that set up memcached for mailman-web like so:
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': os.environ.get('MEMCACHED_HOST', 'memcached') + ':11211',
}
}
The reason seems to be that the python-memcached integration was dropped with django 3.2 (it’s documented for 3.1, but not for 3.2). django-mailman3 1.3.11 requires at least django 3.2.
To fix this, the image should install either pylibmc or pymemcache instead of python-memcached. Users can then switch to the corresponding django backend.
Upgrading from 0.4.5 to 0.4.6 breaks configurations that set up memcached for mailman-web like so:
The reason seems to be that the
python-memcachedintegration was dropped with django 3.2 (it’s documented for 3.1, but not for 3.2).django-mailman31.3.11 requires at least django 3.2.To fix this, the image should install either
pylibmcorpymemcacheinstead ofpython-memcached. Users can then switch to the corresponding django backend.