Python plugins are a bit of a hidden feature since they are still a WIP, but we can fetch a python plugin like this:

            <py-config>
                plugins = ["http://my-awesome-python-plugin.com/plugin/my-plugin.py"]
            </py-config>

Under the hood, we use the same logic as [[fetch]] to try to import the python plugin; providing that we have access, the plugin should be available and usable.

Using a list for plugins is a good and easy way to get plugins into a pyscript app. We could also allow users to use an extended plugin configuration.

Plugin configuration proposed

            <py-config>
              [[plugins]]
                [plugins.hello-world]
                  path = "http://my-awesome-python-plugin.com/plugin/my-plugin.py"
            </py-config>

Or using json

<py-config type="json">
plugins": [
    {
      "hello-world": {
        "path": "http://my-awesome-python-plugin.com/plugin/my-plugin.py"
      }
    }
  ],
</py-config>

This could be a good way to allow users to pass specific configurations to the plugins, for example:

 <py-config>
   [[plugins]]
      [plugins.hello-world]
         path = "http://my-awesome-python-plugin.com/plugin/my-plugin.py"
         coffee = "Yes please"
</py-config>

Pyscript could then use those extra configurations available as hooks for the plugin itself (which I think is the idea of the plugins.configuration.

Some concerns

Using this extended configuration does bring some issues. For once, it will be easier to have a bad config if you don't know toml/json.

The code that ingests the config and looks over the plugins will have to be more complex to handle the more complex structure.