Next Previous

Changes to "pluginconf" between 2022-10-31 11:59:24 and 2022-10-31 12:04:39

1
2
3
4
5
6
7
8
9
10
11

12
13
14



15
16
17
18























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












+
-
-
-
+
+
+




+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

## pluginconf

Is a Python implementation of [PMD](wiki/Plugin+Meta+Data).

| Project | URL                                       |
|---------|-------------------------------------------|
| Repo    | <https://fossil.include-once.org/pluginspec/tree/pluginconf> |
| API     | <https://fossil.include-once.org/pluginspec/doc/tip/html/index.html> |
| pypi    | <https://pypi.org/project/pluginconf/> |
| freshcode | - |

It [originated](http://fossil.include-once.org/streamtuner2/wiki/plugin+meta+data)
It originated in streamtuner2. But has since gained some config dialog
implementation of its own (for modseccfg and other small tools). Simplifies
configuration management, and has a pretty terse API.
in streamtuner2. But has since gained some config dialog implementation of its own
(for modseccfg and other small tools). Simplifies configuration management, and has
a pretty terse API.

 * Only supports Python `#` comments.
 * Works from within pyz/zip packages.
 * Additionally wraps setup() and flit package builds.

### sample

    # api: python
    # title: example
    # description: shows plugin_meta() reading
    ##type: main
    # version: 0.1
    # 
    # Imagine this being a real Python script.

    import pluginconf
    meta = pluginconf.plugin_meta(filename=__file__)
    print(meta.title)

    pluginconf.plugin_base = ["plugins", "contrib"]
    print(pluginconf.all_plugin_meta())

There's also a simplified interface now (pluginconf.bind) for most common
use cases. Though of course it makes most sense, if there are actual
script/extension downloads.