A fault-tolerant pylibmc cache backend for Django
Documentation
By default, a failed cache operation in Django is fatal and will raise a 500 error. In some cases, this might not be desirable behavior. This cache backend will catch failures and log them, but not raise an exception. A cache get that fails will appear to be a miss to the application.
Installation
pip install pylibmc django-ft-cache
Replace the existing pylibmc cache backend in your settings with 'django_ft_cache.FaultTolerantPyLibMCCache'. For example:
CACHES = {
'default': {
'BACKEND': 'django_ft_cache.FaultTolerantPyLibMCCache',
'LOCATION': ['127.0.0.1:11211'],
},
}Building Your Own
If you are already using a custom cache backend, a mixin is provided that should add this capability: django_ft_cache.FaultTolerantCacheMixin.
History
1.0.0 (2017-06-27)
Tests against Django 1.11 and Python 3.6
Bump to stable/production
0.9.0 (2016-02-01)
Tests against Django 1.9 and Python 3.4, 3.5
0.1.0 (2014-07-16)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for django-ft-cache 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django-ft-cache-1.0.0.tar.gz | 3.8 kB | Details |
Release files / django-ft-cache-1.0.0.tar.gz
| Download URL | django-ft-cache-1.0.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4ff9fb7383f73800e187fef56297a52d8463135de8eace214322c08f6432c7e
|
|
BLAKE2b-256 checksum How to use checksums |
41c0443939c47ab0ea664a5a1cf9d3e3d4b061865b4147906ebce167215701cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
