Generate bindings in static location

[mschuwalow]

It would be nice to be able to generate the binding in a static location (not depending on the component world name).

When writing libraries that are used with compentize-py, this is otherwise quite annoying as you cannot use normal imports / locally generated types.

See here for two examples:

• Initial WASI/componentize-py support urllib3/urllib3#3593
• https://github.com/golemcloud/golem-py

[dicej]

There's a --world-module option for the componentize-py bindings subcommand which allows you to override the Python module name (and thus the directory name). For example:

 $ cd $COMPONENTIZE_PY_SOURCE_DIR/examples/cli
 $ cargo run --release --manifest-path ../../Cargo.toml -- -d ../../wit -w wasi:cli/command@0.2.0 bindings --world-module foo bindings
 $ find bindings | head
bindings
bindings/foo
bindings/foo/exports
bindings/foo/exports/__init__.py
bindings/foo/exports/run.py
bindings/foo/types.py
bindings/foo/__init__.py
bindings/foo/imports
bindings/foo/imports/terminal_stderr.py
bindings/foo/imports/insecure_seed.py

Does that suit your needs? If so, I could add a corresponding option to the componentize-py componentize subcommand (or just move the option up so it's common to both subcommands) so it has the same effect there.

[mschuwalow]

Hi, I think that would serve my needs perfectly (especially if there is some default so everybody ends up having their bindings in the same place).

I would appreciate you adding those options, thanks 👍

[dicej]

Let me know if #150 works for you.

[mschuwalow]

Works for me, thank you for your quick help!