This Django application can be used as a backend to the cache system that will keep a backup of cached items even if the value has expired.
All core Django cache backends are provided with the addition of keeping a backup of expired values.
This is for low-level caching interactions.
See the documentation.
1 maintainer
Metadata
1 maintainer
Release files for django-xcache 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-xcache-0.1.tar.gz | 4.2 kB | Without provenance | Details |
Release files / django-xcache-0.1.tar.gz
| Download URL | django-xcache-0.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5587cba4ba2f46927b431aa4b9af6a0cc6298845fd9b999b2ccdd44140bd1a3c
|
|
BLAKE2b-256 checksum How to use checksums |
1ee29a7f344dccb5ca3e19cba085959c0643f2e108c46eab7a67e6aeda98ce14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-xcache 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
