chore(deps): update dependency klepto to v0.2.6 #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==0.2.3
->==0.2.6
Release Notes
uqfoundation/klepto (klepto)
v0.2.6
Compare Source
0.2.6 Release Notes
Klepto extends python's
lru_cache
to utilize different keymaps and alternate caching algorithms, such aslfu_cache
andmru_cache
. While caching is meant for fast access to saved results, klepto also has archiving capabilities, for longer-term storage. Klepto uses a simple dictionary-sytle interface for all caches and archives, and all caches can be applied to any python function as a decorator. Keymaps are algorithms for converting a function's input signature to a unique dictionary, where the function's results are the dictionary value. Thus fory = f(x)
,y
will be stored incache[x]
(e.g.{x:y}
).Klepto provides both standard and 'safe' caching, where safe caches are slower but can recover from hashing errors. Klepto is intended to be used for distributed and parallel computing, where several of the keymaps serialize the stored objects. Caches and archives are intended to be read/write accessible from different threads and processes. Klepto enables a user to decorate a function, save the results to a file or database archive, close the interpreter, start a new session, and reload the function and it's cache.
Klepto installs with pip:
$ pip install klepto
Klepto requires:
- python or pypy, >=3.8
- dill, >=0.3.9
- pox, >=0.3.5
Optional requirements:
- sqlalchemy, >=1.4.0
(install with$ pip install klepto[archives]
)- h5py, >=2.8.0
(install with$ pip install klepto[archives]
)- pandas, >=0.17.0
(install with$ pip install klepto[archives]
)Klepto is licensed under 3-clause BSD:
To cite klepto:
What's Changed
Full Changelog: uqfoundation/klepto@0.2.5...0.2.6
v0.2.5
Compare Source
0.2.5 Release Notes
Klepto extends python's
lru_cache
to utilize different keymaps and alternate caching algorithms, such aslfu_cache
andmru_cache
. While caching is meant for fast access to saved results, klepto also has archiving capabilities, for longer-term storage. Klepto uses a simple dictionary-sytle interface for all caches and archives, and all caches can be applied to any python function as a decorator. Keymaps are algorithms for converting a function's input signature to a unique dictionary, where the function's results are the dictionary value. Thus fory = f(x)
,y
will be stored incache[x]
(e.g.{x:y}
).Klepto provides both standard and 'safe' caching, where safe caches are slower but can recover from hashing errors. Klepto is intended to be used for distributed and parallel computing, where several of the keymaps serialize the stored objects. Caches and archives are intended to be read/write accessible from different threads and processes. Klepto enables a user to decorate a function, save the results to a file or database archive, close the interpreter, start a new session, and reload the function and it's cache.
Klepto installs with pip:
$ pip install klepto
Klepto requires:
- python or pypy, >=3.8
- dill, >=0.3.8
- pox, >=0.3.4
Optional requirements:
- sqlalchemy, >=1.4.0
(install with$ pip install klepto[archives]
)- h5py, >=2.8.0
(install with$ pip install klepto[archives]
)- pandas, >=0.17.0
(install with$ pip install klepto[archives]
)Klepto is licensed under 3-clause BSD:
To cite klepto:
What's Changed
hashlib.algorithms_available
by @IvanaGyro in https://github.com/uqfoundation/klepto/pull/113New Contributors
Full Changelog: uqfoundation/klepto@klepto-0.2.4...0.2.5
v0.2.4
Compare Source
klepto 0.2.4 Release Notes
Klepto extends python's
lru_cache
to utilize different keymaps and alternate caching algorithms, such aslfu_cache
andmru_cache
. While caching is meant for fast access to saved results, klepto also has archiving capabilities, for longer-term storage. Klepto uses a simple dictionary-sytle interface for all caches and archives, and all caches can be applied to any python function as a decorator. Keymaps are algorithms for converting a function's input signature to a unique dictionary, where the function's results are the dictionary value. Thus fory = f(x)
,y
will be stored incache[x]
(e.g.{x:y}
).Klepto provides both standard and 'safe' caching, where safe caches are slower but can recover from hashing errors. Klepto is intended to be used for distributed and parallel computing, where several of the keymaps serialize the stored objects. Caches and archives are intended to be read/write accessible from different threads and processes. Klepto enables a user to decorate a function, save the results to a file or database archive, close the interpreter, start a new session, and reload the function and it's cache.
Klepto installs with pip:
$ pip install klepto
Klepto requires:
- python or pypy, >=3.7
- dill, >=0.3.7
- pox, >=0.3.3
Optional requirements:
- sqlalchemy, >=1.4.0
(install with$ pip install klepto[archives]
)- h5py, >=2.8.0
(install with$ pip install klepto[archives]
)- pandas, >=0.17.0
(install with$ pip install klepto[archives]
)Klepto is licensed under 3-clause BSD:
To cite klepto:
What's Changed
New Contributors
Full Changelog: uqfoundation/klepto@klepto-0.2.3...klepto-0.2.4
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.