OH-MY-PICKLEDB
oh-my-pickleDB is a lightweight, fast, and intuitive data manager written in python
📝 Table of Contents
- About
- Getting Started
- Deployment
- Usage
- Built Using
- TODO
- Contributing
- Authors
- Acknowledgments
- Useful Links
🧐 About
oh-my-pickleDB is an improved version of PickleDB, with notable differences compared to the original. Most important differences are:
- Cryptographic utils - Encrypt/Decrypt data content using FERNET symmetric encryption
- Code improvements - More readable documentation, improved code, etc...
- Data conversions - Byte, json, or str conversions
- More flexibility - Save/load data as bytes, json or str, you decide!
- Utilities - Export data as XML
🏁 Getting Started
Prerequisites
python~=3.9
cryptography~=3.4.8
setuptools~=58.1.0
fire~=0.4.0
Installing
# Using python pip
$ pip install oh-my-pickledb
# Using git
$ git clone https://github.com/tory1103/oh-my-pickledb.git
$ cd oh-my-pickledb
$ pip install -r requirements.txt
$ python setup.py install
🔧 Running the tests
Tests are found on tests folder.
In future versions, tests will be added inside code documentation as multi-row comments.
Break down into end to end tests
cd /tests
python3 <test_name>.py
🎈 Usage
from my_pickledb import PickleDB
database = PickleDB("test.json") # PickleDB object
database.set('key', 'value') # Creates new key and value
database.get('key') # Must return 'value'
database.save.as_json() # Must save database to file on specified path
🚀 Deployment
oh-my-pickleDB is a python library, when installed, just import it to your project.
import my_pickledb
from my_pickledb import *
⛏️ Built Using
- Python
- Json
- Data Structures
✍️ Authors
- @tory1103 - Idea, Concept & Initial work
See also the list of contributors who participated in this project.
🎉 Acknowledgements
✨ Useful links
Metadata
Release files for oh-my-pickledb 0.4.2
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 |
|---|---|---|---|---|
| oh-my-pickledb-0.4.2.tar.gz | 20.9 kB | Without provenance | Details for oh-my-pickledb-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oh_my_pickledb-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for oh_my_pickledb-0.4.2-py3-none-any.whl |
Total release size: 40.5 kB
Release files / oh-my-pickledb-0.4.2.tar.gz
| Download URL | oh-my-pickledb-0.4.2.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11734e047a88757b9b0e2be72f5abc320143e4589c11ab5ee2d95c9f43620440
|
|
BLAKE2b-256 checksum How to use checksums |
6e11fd3c58f9576d475c96381eec97011a65585503ff744e49fd7f086b6ed919
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.9.9
|
Release files / oh_my_pickledb-0.4.2-py3-none-any.whl
| Download URL | oh_my_pickledb-0.4.2-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46f89181964c55039e4d4541c5ba8fea0545e55acaad636ae53e4e4637d16efe
|
|
BLAKE2b-256 checksum How to use checksums |
bbe718a059ddd08c6ad9c2789782746d76d878dd585c8d2b9a202f545c16187f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.9.9
|
Security for oh-my-pickledb 0.4.2
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.