Commit 26b1f79
fix(settings): map removed memcached.MemcachedCache to PyMemcacheCache (#59)
The Django 5.2 upgrade switched the memcached driver to pymemcache, but
deployments upgraded in place from Django 3.x still have
SSM_CACHES_BACKEND=memcached.MemcachedCache persisted in their .ssm-env.
That backend was removed in Django 4.1, so on Django 5 the manager raises
InvalidCacheBackendError and fails to boot.
Transparently remap the dropped alias to memcached.PyMemcacheCache (with a
DeprecationWarning) so existing deployments survive the upgrade without
manual .ssm-env edits. Fresh deployments should set
SSM_CACHES_BACKEND=memcached.PyMemcacheCache directly.
Discovered reviewing the live aiview.com hub, whose .ssm-env still carries
the old backend string.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent ff182ec commit 26b1f79
1 file changed
Lines changed: 17 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
297 | 297 | | |
298 | 298 | | |
299 | 299 | | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
| 304 | + | |
| 305 | + | |
| 306 | + | |
| 307 | + | |
| 308 | + | |
| 309 | + | |
| 310 | + | |
| 311 | + | |
| 312 | + | |
| 313 | + | |
| 314 | + | |
| 315 | + | |
| 316 | + | |
300 | 317 | | |
301 | 318 | | |
302 | 319 | | |
| |||
0 commit comments