This release is a pre-release and may not be stable for production use.
IODict
iodict is a thread safe dictionary implementation which uses a pure python
object store. The dictionary implementation follows the Dict API, but stores
items using their birthtime allowing users to treat this datastore as a
file system backed OrderedDict.
Items in the object store use file system attributes, when available to store key and birthtime information. File system attributes enhance the capability of the object store; however, they're not required. In the event xattrs are not available, file stat is used for file creation time along with base64 encoding for object keys.
Usage
import iodict
data = iodict.IODict(path='/tmp/iodict') # Could be any path on the file system
data["key"] = "value"
data
{'key': "value"}
dir(data)
['__class__',
'__delattr__',
'__delitem__',
'__dict__',
'__dir__',
'__doc__',
'__enter__',
'__eq__',
'__exit__',
'__format__',
'__ge__',
'__getattribute__',
'__getitem__',
'__gt__',
'__hash__',
'__init__',
'__init_subclass__',
'__iter__',
'__le__',
'__len__',
'__lt__',
'__module__',
'__ne__',
'__new__',
'__reduce__',
'__reduce_ex__',
'__repr__',
'__setattr__',
'__setitem__',
'__sizeof__',
'__str__',
'__subclasshook__',
'__weakref__',
'_db_path',
'_encoder',
'_lock',
'clear',
'copy',
'fromkeys',
'get',
'items',
'keys',
'pop',
'popitem',
'setdefault',
'update',
'values']
When running in a multiprocessing / threading application, a lock is required to be passed into the iodict class.
import threading
import iodict
data = iodict.IODict(path='/tmp/iodict', lock=threading.Lock)
By default, if no lock is provided, a multiprocessing lock will be created.
The lock object allows the iodict to respect the locking paradigm of the
executing application.
Metadata
Release files for iodict 0.0.7a20211216194720
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 |
|---|---|---|---|---|
| iodict-0.0.7a20211216194720.tar.gz | 9.5 kB | Without provenance | Details for iodict-0.0.7a20211216194720.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iodict-0.0.7a20211216194720-py3-none-any.whl | Python 3 | none | any | Details for iodict-0.0.7a20211216194720-py3-none-any.whl |
Total release size: 19.9 kB
Release files / iodict-0.0.7a20211216194720.tar.gz
| Download URL | iodict-0.0.7a20211216194720.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9fbfde36c205fd94cb3d2d91ccf69d284c542e38724496dfced8636622133533
|
|
BLAKE2b-256 checksum How to use checksums |
307a6bcad81a0a140a12a1d776df35b6393c93cb5e2f82c41036f7f934345c47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.3 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Release files / iodict-0.0.7a20211216194720-py3-none-any.whl
| Download URL | iodict-0.0.7a20211216194720-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e607504b3b893a63d3eb531afd7e5c07e055511b633a02a7715e4c26a1150163
|
|
BLAKE2b-256 checksum How to use checksums |
18dd504f92ce384233045bf1b656c9927c7e43fe12221213cf9f46108c9c7efe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.3 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Security for iodict 0.0.7a20211216194720
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.