README.rst edit
Dave Cinege
3 years ago
72 | 72 | release. As such, both modules are very subject to change at this time. |
73 | 73 | Specifically I have the following decisions to make: |
74 | 74 | |
75 | - Finalize name conventions. Use set_path() or setpath()? | |
75 | - Finalize name conventions. Use set_path() or setpath()? | |
76 | 76 | |
77 | - Finalize specialtiy method names, Are merge(), mesh() and | |
78 | screen() good names that make sense? I am struggling with the | |
79 | ThesaurusExtended method names myself. | |
77 | - Finalize specialtiy method names, Are merge(), mesh() and | |
78 | screen() good names that make sense? I am struggling with the | |
79 | ThesaurusExtended method names myself. | |
80 | 80 | |
81 | - Resolve Thesaurus's schizophrenia. | |
82 | :: | |
83 | v = t['a.b.c'] # This recurses | |
84 | t['a.b.c'] = v # This does not. Use set_path() | |
81 | - Resolve Thesaurus's schizophrenia. | |
82 | .. code:: python | |
83 | v = t['a.b.c'] # This recurses | |
84 | t['a.b.c'] = v # This does not. Use set_path() | |
85 | 85 | |
86 | I want to be comfortable this feels naturale to others or make | |
87 | changes. | |
86 | I want to be comfortable this feels naturale to others or make | |
87 | changes. | |
88 | 88 | |
89 | - Review how I do recursive copy/deepcopys. | |
89 | - Review how I do recursive copy/deepcopys. | |
90 | 90 | |
91 | - Decide how to properly handle copying ThesaurusCfg coercion methods. | |
91 | - Decide how to properly handle copying ThesaurusCfg coercion methods. | |
92 | 92 | |
93 | 93 | |
94 | 94 | |
116 | 116 | The effect is to syntatically reference keys like attributes. |
117 | 117 | |
118 | 118 | For example: |
119 | .. code:: python | |
119 | .. code::python | |
120 | 120 | t['k'] |
121 | 121 | t.k |
122 | 122 |