1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225
|
<div align="center">
# Python Super Collections
**Dictionaries as you dreamed them when you were a kid.**
Instantly Convert json and YAML files into objects with attributes.
</div>
```python
import json
from super_collections import SuperDict
with open('my_file.json', 'r') as file:
data = json.load(file)
document = SuperDict(data)
print(document.author) # instead of document['author']
for document in document.blocks: # instead of document['blocks']
...
print(document.blocks[3].name) # instead of document['blocks'][3]['name'] -- eek! 🤢
```
________
<!-- To update, run the following command:
markdown-toc -i README.md
-->
<!-- toc -->
- [Python Super Collections](#python-super-collections)
- [How it works](#how-it-works)
- [Superdicts](#superdicts)
- [Superlists](#superlists)
- [Why Combining SuperDicts with SuperLists?](#why-combining-superdicts-with-superlists)
- [Install](#install)
- [From the repository](#from-the-repository)
- [Usage](#usage)
- [Remarks](#remarks)
- [Restrictions](#restrictions)
- [Does it work?](#does-it-work)
- [When are superdictionaries and superlists _not_ recommended?](#when-are-superdictionaries-and-superlists-not-recommended)
- [Related data structures and ideas](#related-data-structures-and-ideas)
- [Standard Python](#standard-python)
- [Dot notation on dictionaries](#dot-notation-on-dictionaries)
- [Using superlists to complement superdictionaries](#using-superlists-to-complement-superdictionaries)
<!-- tocstop -->
## How it works
There are several packages that quickly convert json or YAML files into
dictionaries that contain dictionaries, lists etc.
If you want to properly use those data structures in Python, one solution is
to create specific classes.
But sometimes, it is overkill. You just want your app to quickly load
structured data and navigate through them.
That's where the **super-collections** package (**SuperDict** a **SuperList**) comes handy.
### Superdicts
> 📝 **Definition** <br> A **superdictionnary** is a dictionary whose keys (at least those that are valid identifiers) are automatically accessible as attributes, with the **dot notation*.
```python
d = SuperDict({'foo':5, 'bar': 'hello'})
# instead of writing d['foo']
d.foo = 7
```
> Several other languages, such as Javascript, LUA, Ruby, and PHP offer that **dot notation**
> in some form or other. However, implementing that idea is not as
> straightforward as it seems.
> The idea of superdictionaries in Python has been around for some time
> (see the [superdict](https://github.com/itdxer/superdict) packagage by Yuri
> Shevchuk, 2015).
> 📝 **Property** <br> If a SuperDict object contains a value that is itself a dictionary, that dictionary is then converted in turn into a SuperDict.
### Superlists
A **superlist** is a list where all dictionary items have been
(automagically) converted to **superdictionnaries**.
> ⚠️ **Superlists are indispensable** <br> They were the missing piece of the jigsaw puzzle;
> without them, it is not possible to convert deep data structures into supercollections.
### Why Combining SuperDicts with SuperLists?
The structure of JSON, YAML or HTML data is generally a deeply nested combination of dictionaries and lists. Using superdictionaries alone would not be sufficient, since lists within the data contained in a list would still contain regular (unconverted) dictionaries; this would require you to switch back to the standard dictionary access method.
By combining superdictionaries and superlists,
it is possible to ensure that all nested dictionaries within lists will also be converted to SuperDicts, allowing for a consistent dot notation throughout the entire data structure.
> 💡 **Deep conversion** <br> SuperLists objects, combined with SuperDicts make sure that the most complex
> datastructures (from json or YAML) can be recursively converted into
> well-behaved Python objects.
## Install
### From the repository
```sh
pip install super-collections
```
## Usage
```python
from super_collections import SuperDict, SuperList
d = SuperDict({'foo':5, 'bar': 'hello'})
l = SuperList([5, 7, 'foo', {'foo': 5}])
```
You can cast any dictionary and list into its "Super" equivalent when you want, and you are off to the races.
**The casting is recursive** i.e. in the case above, you can assert:
```python
l[-1].foo == 5
```
All methods of dict and list are available.
Those objects are self documented. `d.properties()` is a generator
that lists all keys that are available as attributes.
The `__dir__()` method (accessible with `dir()`) is properly updated with
those additional properties.
```python
list(d.properties())
> ['foo', 'bar']
dir(d)
> ['__class__', ..., 'bar', 'clear', 'copy', 'foo', 'fromkeys', 'get', 'items', 'keys', 'pop', 'popitem', 'properties', 'setdefault', 'to_hjson', 'to_json', 'update', 'values']
```
This means the **auto-complete feature** might be available
for the attributes of a SuperDict within a code editor (if the dictionary was
statically declared in the code); or in an advanced REPL
(such as [bpython](https://bpython-interpreter.org/)).
The methods `dict.update(other_dict)` and `list.extend(other_list)`
automatically cast the contents into SuperDict and SuperList as needed.
## Remarks
### Restrictions
1. In a SuperDict, **only keys that are valid Python identifiers
can be accessed as attributes**. If 'bar' is a key of object `foo`,
you can write `foo.bar`; but you can't
write ~~`foo.hello world`~~ because 'hello world' is not a
valid Python identifier;
you will have to access that specific value with the "dictionary" notation:
`foo['hello world']`.
2. Similarly, you can't use pre-existing methods of the
`dict` class: `keys`, `items`, `update`, etc. as properties; as well as the
`properties` method itself (wich is specific to SuperDict).
In that case again, use the dictionary notation to access
the value (`d['items']`, etc.). Those keys that
cannot be accessed as attributes are said to be **masked**.
If you are uncertain which are available, just use `SuperDict.properties()`.
method.
3. Updating a single element (`d['foo']` for a SuperDict and `l[5]`
for a SuperList) does not perfom any casting. That's to avoid crazy
recursive situations, while giving
you fine grain control on what you want to do
(just cast with `SuperDict()` and `SuperList()`).
### Does it work?
Yes. It is tested with pytest. See the `test` directory for examples.
### When are superdictionaries and superlists _not_ recommended?
SuperDicts (and SuperLists) classes are most useful when the program you are
writing is consuming loosely structured data (json, YAML, HTML)
you have every reason to believe they
are sufficiently well-formed: typically data exported from existing APIs
or Web sources.
> ⚠️ **Caution** <br> super-collections may not be the best
> tool when source data come from a source whose quality
> is unsufficiently guaranteed for your needs, or is untrusted.
If you want to impose strongly formatted data structures in your code, one solution is
to create [dataclasses](https://docs.python.org/3/library/dataclasses.html); especially those of [Pydantic](https://docs.pydantic.dev/latest/concepts/dataclasses/), which make implicit and explicit
controls on the integrity of the source data.
## Related data structures and ideas
These projects contain ideas that inspired or predated super-collections.
### Standard Python
* `collections.namedtuple`: tuples with dot notation ([standard python class](https://docs.python.org/3/library/collections.html#collections.namedtuple))
* `types.SimpleNamespace`: objects with arbitrary attributes ([standard python class](https://docs.python.org/3/library/types.html#types.SimpleNamespace))
* All Python classes have a __dict__ attribute, used at the foundation to implement the dot notation in the language, with the relative standard methods (`__setattr__()`, etc.) and functions (`setattr()`, etc.).
* In modern Python, the `dict` class has ordered keys (by insertion order) and is subclassable.
### Dot notation on dictionaries
* [addict](https://github.com/mewwts/addict) (Github)
* [DotMap](https://github.com/drgrib/dotmap): subclasses and MutableMapping and OrderedDict (Github)
* [SuperDict](https://github.com/itdxer/superdict): subclasses `dict` (Github)
* [dotty_dict](https://github.com/pawelzny/dotty_dict): wrapper (Github)
### Using superlists to complement superdictionaries
* Packages that write to and read from files, such as [shelve](https://docs.python.org/3/library/shelve.html) (standard), json, YAML, [Beautifulsoup](https://code.launchpad.net/beautifulsoup/), etc. heavily rely
on a **combination of dictionaries and lists**. BeautifulSoup in particular supports dot notation.
* In general, **the construction of any syntactic or semantic tree requires both dictionaries and lists**.
|