django-memoize
django-memoize is an implementation of memoization technique for Django. You can think of it as a cache for function or method results.
Release files for django-memoize 2.3.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-memoize-2.3.1.tar.gz | 23.2 kB | Without provenance | Details |
Release files / django-memoize-2.3.1.tar.gz
| Download URL | django-memoize-2.3.1.tar.gz |
|---|---|
| Size | 23.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62ac4807710ecf22a7397d008d64d0f798e7230482d4b6072d916cac852a47cd
|
|
BLAKE2b-256 checksum How to use checksums |
b4c0812c5f50957eed4c83017f7c1d9a095a8f8dba1f3c1286d07932eff5b7b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.6.0 requests-toolbelt/0.8.0 tqdm/4.40.1 CPython/3.7.0
|
Security for django-memoize 2.3.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.
