39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
What for then?
> * Separates code from meta data. Avoids keeping seldomly used descriptors in variables.
> * Does away with externalized ini/json files for modules, yet simplifies use of external tooling.
> * Minimizes premature module loading just to inspect meta information.
pluginconf is foremost about the universal meta comment format.
|
<
<
|
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
What for then?
> * Separates code from meta data. Avoids keeping seldomly used descriptors in variables.
> * Does away with externalized ini/json files for modules, yet simplifies use of external tooling.
> * Minimizes premature module loading just to inspect meta information.
# API
Lookup configuration is currently just done through injection:
plugin_base = [__package__, "myapp.plugins", "/usr/share/app/extensions"]
module_base = "pluginconf" # or any top-level app module
|
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
|
# flit wrapper
Alternatively, there's `pluginconf.flit` to utilize pyproject.toml for
building packages, while sourcing meta data from the primary package file.
[build-system]
requires = ["flit_core", "pluginconf"]
build-backend = "pluginconf.flit"
[project]
name = "projectname"
It can be invoked via `python -m pluginconf.flit build` or even
`flit-pluginconf build`. Field mapping isn't very robust yet.
## other modules
* `pluginconf.depends` provides `Check` for .valid() and .depends() probing
* argparse_map() might also end up in a separate module.
|
|
|
|
>
>
|
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
|
# flit wrapper
Alternatively, there's `pluginconf.flit` to utilize pyproject.toml for
building packages, while sourcing meta data from the primary package file.
[build-system]
requires = ["pluginconf", "flit"]
build-backend = "pluginconf.flit"
[project]
name = "projectname"
It can be invoked via `flit-pluginconf build` / `python -m pluginconf.flit build`
or even `python -m build`. Field mapping isn't very robust yet, and mercilessly
flaunts the `dynamic=` directive.
## other modules
* `pluginconf.depends` provides `Check` for .valid() and .depends() probing
* argparse_map() might also end up in a separate module.
|