PersistedState
Simple and fast solution for persisting small states:
from persistedstate import PersistedState
STATE = PersistedState("example.state", last_id=0)
for current_id in range(STATE.last_id + 1, 100_001):
print(f"Processing item #{current_id}")
STATE.last_id = current_id
print("Processing DONE.")
You can interrupt this script, and next time it will continue from the first unprocessed item. As another example see benchmarks/perftest.py.
Mapped YAML state file
The use case is persisting small amount of data which can be edited easily with a text editor. The database is an UTF-8 encoded YAML file, so it can be highlighted and edited manually if needed. (It also uses YAML stream file format for journal.) The YAML file is fully mapped to Python objects, so every change is synchronized to disk immediately. E.g. you can do this:
STATE = PersistedState("state.yaml", processed_items=[])
STATE.setdefault("key", {})
STATE["key"].setdefault("nested", 2)
STATE.processed_items.append("<some item>")
STATE["key"]["nested"] += 1
Note: slice operations on lists are not supported (e.g. state.mylist[1:3]). Use individual index access instead.
Failure tolerance
It uses Write-Ahead-Logging and atomic vacuum, so there will be no data loss.
Thread safe
Changing the state is thread safe. You also can use the ._thread_lock attribute to make atomic changes:
def atomic_increment():
with STATE._thread_lock:
STATE.counter += 1
Performance
For its use case it outperforms existing key-value store modules. For example incrementing a counter (for the details see benchmarks/perftest.py):
state.counter = 0
for _ in range(COUNT_TO):
state.counter += 1
Counting to 10,000 (using Windows and Python 3.11):
PersistedState 0.193 sec
DiskCache 1.222 sec
SqliteDict 3.089 sec
Lmdb 14.944 sec
Shelve 39.771 sec
The example seems to be silly, but this is very close to the use case it was developed for. For complex data structures or big amount of data I suggest using other libraries, like DiskCache. (The rule of thumb is when your state file is too big to be edited easily in your favorite text editor, you may think about using another key-value store library.)
Metadata
Release files for persistedstate 26.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 | |
|---|---|---|---|---|
| persistedstate-26.1.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| persistedstate-26.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.3 kB
Release files / persistedstate-26.1.tar.gz
| Download URL | persistedstate-26.1.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bc85046bc6996067e4603888b0e2c8b337549f7a3cf8a3f3ae8411fc4e48bad
|
|
BLAKE2b-256 checksum How to use checksums |
55c751c214c147cfbedd2ea34c1ae84f4178a1f19c145c637b8ba136b60736a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / persistedstate-26.1-py3-none-any.whl
| Download URL | persistedstate-26.1-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a3fbc2c47284cccb5749b6128698b6cb77e51d84230606c4b5c2dcc4a2e5388
|
|
BLAKE2b-256 checksum How to use checksums |
35067cb7ae5b01007127360fbe75481ea353347c60e9642343c44f08c30304aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for persistedstate 26.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.