pysolcache
Welcome to pysol
Copyright (C) 2013/2025 Laurent Labatut / Laurent Champagnac
pysolcache is a set of python caches : in-memory and/or redis.
Usefull to handle L1 (memory) and L2 (redis) cache for python daemons.
In all cases, serialization/deserialization of stored datas have to be done at client side (ie, serialize as u wish, ujson or equivalent)
All caches are instrumented by Meters (pysolmeters).
MemoryCache:
- A pure python memory cache storing string/binary keys to string/binary values
- Max bytes capped
- Max items count capped
- Items TTLs
- LRU evictions
- Watchdog evictions
RedisCache:
- A redis backed cache, storing string/binary keys to string/binary values
HighCache:
- A high level cache, coupling MemoryCache adn RedisCache, which handle respectively L1 cache (in memory) and L2 cache (inside redis)
HighCacheEx:
- A high level cache, storing internal data as tuple (ms_added, ttl_ms, string/binary data)
- Provided same level of functionality as HighCache but is able to perform an automatic L1 put in case of L2 hit and L1 miss
It is gevent (co-routines) based.
1 maintainer
Metadata
1 maintainer
Release files for pysolcache 3.13.4
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 | Actions |
|---|---|---|---|---|
| pysolcache-3.13.4.tar.gz | 22.5 kB | Without provenance | Details for pysolcache-3.13.4.tar.gz |
Release files / pysolcache-3.13.4.tar.gz
| Download URL | pysolcache-3.13.4.tar.gz |
|---|---|
| Size | 22.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
214f963cb9b2eb5d7531e218fdb2f23e56f4cbf3712121984615baa33a2858e8
|
|
BLAKE2b-256 checksum How to use checksums |
e4c8982181e968755805a4e64abdc5c2ae7c28dd12173c0f95a224655299ebab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for pysolcache 3.13.4
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
