Cachalot


Cachalot is a minimal persistent memoization cache. It provides a decorator, that stores function result for future use. Perfect for heavy computations and I/O operation (such as web requests). On backend, it uses TinyDB for storage.
Features
- Simple usage via decorator
- Persistent caching
- Key expiration
- Maximum cache size, to prevent bloat
Installation
Cachalot requires Python 3.5 or newer to run.
Python package
You can easily install Cachalot using pip:
pip3 install cachalot
Manual
Alternatively, to get the latest development version, you can clone this repository and then manually install it:
git clone git@gitlab.com:radek-sprta/cachalot.git
cd cachalot
python3 setup.py install
Usage
from cachalot import Cache
@Cache()
def expensive_function():
return expensive_calculation()
Advanced usage
from cachalot import Cache
@Cache(path='cache.json', timeout=3600, size=5e3, filesize=1e6, retry=True, renew_on_read=True)
def expensive_function():
return expensive_calculation()
path: Path to the database file. Defaults to .cache.json.timeout: How long should the data be cached in seconds. Defaults to 0 (infinite).size: Maximum number of keys cached. Defaults to 0 (infinite).filesize: Maximum size of database file in bytes. Defaults to 0 (infinite).retry: Retry if result is blank. Defaults to False.renew_on_read: Renew the entry, i.e refresh the entry timestamp on reads. Defaults to True
Manually deleting entries
If you want to manually invalidate an entry, you can calculate the hash of the function call and then pass it the remove method.
key = cache.calculate_hash(len)('teststring')
cache.remove(key)
For more information, see documentation.
Contributing
For information on how to contribute to the project, please check the Contributor's Guide
Contact
incoming+radek-sprta/cachalot@gitlab.com
License
MIT License
Credits
This package was created with Cookiecutter and the python-cookiecutter project template. Inspired by Cashier
Metadata
Release files for Cachalot 1.4.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 | Provenance | |
|---|---|---|---|---|
| Cachalot-1.4.0.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Cachalot-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.3 kB
Release files / Cachalot-1.4.0.tar.gz
| Download URL | Cachalot-1.4.0.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93805b5fcd3bfae0cab6c226f61afe027717fad076e7bf37c9b3615627ffa798
|
|
BLAKE2b-256 checksum How to use checksums |
40b097de8d5445f396adb0e841a868750aed08e7d845c3ae2ceeb9bfdaa4af0a
|
| 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/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.10
|
Release files / Cachalot-1.4.0-py3-none-any.whl
| Download URL | Cachalot-1.4.0-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14234b10ec5d92a82f192766af8d7cee4b47c1fb0d86bd488c644cebbd5c1eab
|
|
BLAKE2b-256 checksum How to use checksums |
6c250a4f3d38f020fd0527d84f0dcf2a5aae09ac0b53fa93850e22f026217487
|
| 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/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.10
|
Security for Cachalot 1.4.0
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.