my Sweet Cache
This project let make fast and simply cache
autors
Bartłomiej Chwiłkowski (github: chwilko)
Structure
mySweetCache: mySweetCache.py: main functions utils.py: other function usefull to
Functions
cache
def cache(
MSC_name: Optional[str] = None,
*,
header: Optional[str] = None,
sep_in_data: str = "",
) -> Callable:
Wrapper add possibility caching function result to wrapped function
If file MSC_name exist in _CACHE_FILES wraped function return cache from right cache. else make new cache Wrapper add optional argument 'use_cache'. If use_cache == False cache will overwrite.
Args: MSC_name (Optional[str], optional): cache key. Defaults to None. header (Optional[str], optional): data description. Defaults to None. sep_in_data (str, optional): Separator between array items for text output. If "" (empty), a binary file is written, equivalent to file.write(a.tobytes()). Defaults to "".
Returns: callable: Function with cache functionality.
read_cache
def read_cache(MSC_name: str) -> Any:
Function to fast read MSC.
Args: MSC_name (str): cache key to read.
Raises: NameError: If this cache don't exist.
Returns: np.array: Previously saved data.
save_cache
save_cache(
MSC_name: str,
data: ndarray,
*,
header: Optional[str] = None,
sep_in_data: str = "",
)
Function to fast save MSC.
Args: MSC_name (str): cache key to save. data (ndarray): data to save sep_in_data (Optional[str], optional): Separator between array items for text output. If "" (empty), a binary file is written, equivalent to file.write(a.tobytes()).
use_par
Decorator set self argument as first function argument.
def use_par(par):
use_pars
Decorator set self arguments as first function arguments.
def use_pars(*pars):
How to use
example use:
@cache("key")
def long_working_function() -> np.ndarray:
# long code to work
return ...
example use 2:
@cache("key")
@use_parms(11, 21)
def long_working_function(arg1, arg2) -> np.ndarray:
# long code to work
return ...
After first call this function result is saved in .MScache_files/key
In next call instead recount value will be read from cache.
To recount call long_counting_function(use_cache=False) then cache will be overwrited
or delete .MScache_files/try file.
WARNING! If you define two function with the same key, there two functions will share the same cache file.
Licence
MIT
Metadata
Release files for mySweetCache 1.1.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 | Actions |
|---|---|---|---|---|
| mysweetcache-1.1.0.tar.gz | 36.7 kB | Without provenance | Details for mysweetcache-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mysweetcache-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for mysweetcache-1.1.0-py3-none-any.whl |
Total release size: 44.1 kB
Release files / mysweetcache-1.1.0.tar.gz
| Download URL | mysweetcache-1.1.0.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7cf74644e06bf03791d5b1125f3d36fbfc3873d87a1e1e5fceed78b11a3b5f26
|
|
BLAKE2b-256 checksum How to use checksums |
ebe9f4ea9826c72a17a522b2f8098569f3f688d4c90ed317358ec10893fd2c9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / mysweetcache-1.1.0-py3-none-any.whl
| Download URL | mysweetcache-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5923cc443de1249d80bf095d7cc50d0cf208ad8c0978fe1d1432450df7be6b4a
|
|
BLAKE2b-256 checksum How to use checksums |
8df5bc5fb04e5230658a6941be0ea40ea1b2fcb6c525475ba5561f95546bf453
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for mySweetCache 1.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.