Can't write plugins solely with `--enable-python-plugins`
If the user builds and install the project:
./configure --enable-python-plugins make make install
They won't be able to do the
import bt2 necessary to start defining their BT2 plugin.
To write a Python plugin , the user needs to use the Python bindings as well.
The user gets this:
>>> import bt2 Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'bt2'We could either:
- turn on `--enable-python-bindings` whenever `--enable-python-plugins` is enabled,
- error out during the ./configure if `--enable-python-bindings` is not provided.
Updated by Simon Marchi almost 3 years ago
I would suggest that using --enable-python-plugins automatically enables the python bindings, as long as --disable-python-bindings is not provided. In other words, this table:
plugins | bindings --------+--------- missing | missing -> both disabled missing | enable -> plugins disabled, bindings enabled missing | disable -> both disabled enable | missing -> both enabled enable | enable -> both enabled enable | disable -> error disable | missing -> both disabled disable | enable -> plugins disabled, bindings enabled disable | disable -> both disabled
Updated by Francis Deslauriers almost 3 years ago
- Status changed from Waiting for review to Resolved