lilcache
Interprocess and thread safe light weight cache
Note: This is under development and has bad performance (concurrency, response time, error prone, etc. you name it!). It is not ready for production use. If you like taking risks, I won't stop you from using it.
Timeline
- Write unittests
- Stress testing
- Improve error handling
- Extension to current implementation: Implement connection pool and client reuse connections
- Implementation 2: Twisted bsaed concurrency
- Implementation 3: Incordinated cache (file db + locks for synchronization)
- For each implementation, perform benchmark tests and stress testing
- Release to PyPi
- Implementation 4: Named PIPE based approach and full duplex communication
- Add more features (snapshot, Cache expiry, etc.)
- Production ready code
Metadata
Release files for lilcache 0.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 | |
|---|---|---|---|---|
| lilcache-0.0.1.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lilcache-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / lilcache-0.0.1.tar.gz
| Download URL | lilcache-0.0.1.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bebd88bd114b9af3ff3182a582c6807e5b07e82c2567bc916ea2ad9f375d8296
|
|
BLAKE2b-256 checksum How to use checksums |
465b71def114ef00185d371b5540c396100937dd0df802b91b9bcd642bfaa7fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.5
|
Release files / lilcache-0.0.1-py3-none-any.whl
| Download URL | lilcache-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a21fbb77d7045205faf226c95bcb1717e0f0f622c91d7d5285125751d3b6b560
|
|
BLAKE2b-256 checksum How to use checksums |
293016a325fbda5fd704b1501831e27cabac06c6611fc501f381df1adccd7411
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.5
|
Security for lilcache 0.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.