This release is a pre-release and may not be stable for production use.
Key to Multivalue Storage - kms
kms - a tiny side project tuned into a library.
JSON storage wrapper and editor. Created with love by Boss_1s.
Once upon a time, this was just a small project to solve a problem: the over-steep learning curve for scratchattach's database functionality. Now, I have decided to make it a library, something with humble beginnings with big hopes in its future.
This is, after all, the greatest piece of a CPython progam I have made. ;)
🚀 What's New in kms-semver1.4.0a0
💡 Features & Automation
- Oops, none yet here. Try checking somewhere else.
🪲 Bug Fixes
- Oops, none yet here. Try checking somewhere else.
⏰ Infrastructure & CI
- Oops, none yet here. Try checking somewhere else.
Badges
Download
Status
Info & Docs
Installation
Install with pip:
pip install -U key-multivalue-storage
Or, download the latest version of the .whl file in the releases page
You can also choose to download the development environment alongside the package:
pip install -U key-multivalue-storage[dev]
The development package includes Pylint for testing and Griffe for finding breaking changes. You can see every test script in the repo's test folder.
Usage
- Create a Storage object to wrap the data to be stored:
>>> from key_multivalue_storage import Storage
>>> my_db = Storage("my_top_level_key", mysubkey="myvalue", myothersk="anotherval")
- To store the object, use
Storage.store().
>>> my_db.store("database.json")
Data stored successfully in 'database.json'.
- You can change certain global variables for each
Storageinstance.
>>> Storage.indent = 4 # indent size of JSON files
>>> Storage.encode = True # Whether to encode stored values
- Load the data back into a Storage object:
>>> import key_multivalue_storage as kms
>>> loaded_db = kms.Load.by_key("database.json", "my_top_level_key") # You can also use Storage.Load.by_key()
>>> loaded_db = my_db
True
- You can also cast a Storage object into a dictionary!
>>> dict_db = dict(my_db)
>>> dict_db
{"my_top_level_key":{"mysubkey":"myvalue","myothersk":"anotherval"}}
There's a lot more to this library that what meets the eye.
See the full documentation here!
Contribute
Roadmap
Report a Bug
Have a GREAT day/night! :)
1 maintainer
Metadata
1 maintainer
Release files for key-multivalue-storage 1.4.0.20261001a0.dev1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| key_multivalue_storage-1.4.0.20261001a0.dev1.tar.gz | 54.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| key_multivalue_storage-1.4.0.20261001a0.dev1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.0 kB
Release files / key_multivalue_storage-1.4.0.20261001a0.dev1.tar.gz
| Download URL | key_multivalue_storage-1.4.0.20261001a0.dev1.tar.gz |
|---|---|
| Size | 54.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28d8e17722fdc780d36b4fc80397a7c16f206d24773983e2413a963a49c6e20b
|
|
BLAKE2b-256 checksum How to use checksums |
62641a2f087c949f402937fe1ba3bf2e0072c28dfcf0962c43fd236f40d7bfa0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / key_multivalue_storage-1.4.0.20261001a0.dev1-py3-none-any.whl
| Download URL | key_multivalue_storage-1.4.0.20261001a0.dev1-py3-none-any.whl |
|---|---|
| Size | 42.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
505674c0f5a017a621776f1ba1dfae576e7912b155bfdbbab4344a80cb1c25bc
|
|
BLAKE2b-256 checksum How to use checksums |
003ed1e023fdf4710f2ad18a86c00857f034f15db1dc240dee05619d8c907954
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log
