MetaDict
Enabling dot notation and IDE autocompletion
Installation • Features • Documentation • Competitors • Citation
MetaDict is designed to behave exactly like a dict while enabling (nested) attribute-style key access/assignment with IDE autocompletion support.
Many libraries claim to do the same, but fail in different ways (see Competitors).
Installation
$ pip install metadict
Features
- Attribute-style key access and assignment (dot notation) with IDE autocompletion support
from metadict import MetaDict cfg = MetaDict() cfg.optimizer = 'Adam' print(cfg.optimizer) >> Adam
- Nested key assignment similar to
defaultdictfromcollectionscfg = MetaDict(nested_assignment=True) cfg.model.type = 'Transformer' print(cfg.model.type) >> Transformer # or restrict nested assignment via context manager cfg = MetaDict() with cfg.enabling_nested_assignment() as cfg: cfg.model.type = 'Transformer' cfg.new_model.type = 'MLP' >> AttributeError: 'MetaDict' object has no attribute 'new_model'
- Is a
dictdict_config = {'model': 'Transformer', 'optimizer': 'Adam'} cfg = MetaDict(dict_config) print(isinstance(cfg, dict)) >> True print(cfg == dict_config) >> True
- Inbuilt
jsonsupportimport json cfg = MetaDict({'model': 'Transformer'}) print(json.loads(json.dumps(cfg))) >> {'model': 'Transformer'}
- Recursive conversion to
dictcfg = MetaDict({'models': [{'name': 'Transformer'}, {'name': 'MLP'}]}) print(cfg.models[0].name) >> Transformer cfg_dict = cfg.to_dict() print(type(cfg_dict['models'][0])) >> <class 'dict'> # Note: Appending a `dict` to a list within a `MetaDict` does not convert the `dict`. # MetaDict does not overwrite `list` so intercepting `append`. `extend`, etc. is currently not possible. # Simply wrap the appended or extended `dict` as a `MetaDict`. cfg.models.append({'name': 'RNN'}) print(isinstance(cfg.models[-1], MetaDict)) >> False cfg.models.append(MetaDict({'name': 'RNN'})) print(isinstance(cfg.models[-1], MetaDict)) >> True
- No namespace conflicts with inbuilt methods like
items(),update(), etc.cfg = MetaDict() # Key 'items' is assigned as in a normal dict, but a UserWarning is raised cfg.items = [1, 2, 3] >> UserWarning: 'MetaDict' object uses 'items' internally. 'items' can only be accessed via `obj['items']`. print(cfg) >> {'items': [1, 2, 3]} print(cfg['items']) >> [1, 2, 3] # But the items method is not overwritten! print(cfg.items) >> <bound method Mapping.items of {'items': [1, 2, 3]}> print(list(cfg.items())) >> [('items', [1, 2, 3])]
- References are preserved
params = [1, 2, 3] cfg = MetaDict({'params': params}) print(cfg.params is params) >> True model_dict = {'params': params} cfg = MetaDict(model=model_dict) print(cfg.model.params is params) >> True # Note: dicts are recursively converted to MetaDicts, thus... print(cfg.model is model_dict) >> False print(cfg.model == model_dict) >> True
Documentation
Check the Test Cases for a complete overview of all MetaDict features.
Competitors
- Addict
- No key autocompletion in IDE
- Nested key assignment cannot be turned off
- Newly assigned
dictobjects are not converted to support attribute-style key access - Shadows inbuilt type
Dict
- Prodict
- No key autocompletion in IDE without defining a static schema (similar to
dataclass) - No recursive conversion of
dictobjects when embedded inlistor other inbuilt iterables
- No key autocompletion in IDE without defining a static schema (similar to
- AttrDict
- No key autocompletion in IDE
- Converts
listobjects totuplebehind the scenes
- Munch
- Inbuilt methods like
items(),update(), etc. can be overwritten withobj.items = [1, 2, 3] - No recursive conversion of
dictobjects when embedded inlistor other inbuilt iterables
- Inbuilt methods like
- EasyDict
- Only strings are valid keys, but
dictaccepts all hashable objects as keys - Inbuilt methods like
items(),update(), etc. can be overwritten withobj.items = [1, 2, 3] - Inbuilt methods don't behave as expected:
obj.pop('unknown_key', None)raises anAttributeError
- Only strings are valid keys, but
Citation
@article{metadict,
title = {MetaDict - Enabling dot notation and IDE autocompletion},
author = {Hillebrand, Lars},
year = {2022},
publisher = {GitHub},
journal = {GitHub repository},
howpublished = {\url{https://github.com/LarsHill/metadict}},
}
Metadata
Release files for metadict 0.1.5
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 |
|---|---|---|---|---|
| metadict-0.1.5.tar.gz | 10.9 kB | Without provenance | Details for metadict-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| metadict-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for metadict-0.1.5-py3-none-any.whl |
Total release size: 22.1 kB
Release files / metadict-0.1.5.tar.gz
| Download URL | metadict-0.1.5.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ebd972a4bd1d22e72a158bfc6ff8d497deab7ab220fa27ad128fcee4f54f300
|
|
BLAKE2b-256 checksum How to use checksums |
d1e1b1831cf30286259e8250c9ec2814cc27c1110a91437723f85fb5b74138ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / metadict-0.1.5-py3-none-any.whl
| Download URL | metadict-0.1.5-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e374cf55cd7e182135f35c50f9c4e83b8f0d70e74b626f6c4499a01267ad0f80
|
|
BLAKE2b-256 checksum How to use checksums |
5b62526f926e3cfbc0cd136480b5902f920502aa41a0c914db3e20ea2804d64c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for metadict 0.1.5
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.