On Wed, 25 Oct 2023, at 11:23 PM, Abhilash Raj wrote:
On 10/25/23 01:04, Thomas Ward via Mailman-users wrote:
Running into some nasty issues.
I have a structure like this, installed as a package in the workspace once installed by pip in the venv:
mailman_customizations/ __init__.py hooks.py <-- plugin definition in here as MailmanCustomizations for class name handlers/ __init__.py handlers.py <-- custom handler in here pipelines/ __init__.py pipelines.py <-- custom pipelines which implement the handlers here.
However, whenever I specify this in config with this clause:
[plugin.MailmanCustomizations] class: mailman_customizations.hooks.MailmanCustomizations enabled: no
Change this to
[plugin.mailman_customizations] class: mailman_customizations.hooks.MailmanCustomizations enabled: yes
FWIW You can also do:
[plugin.MailmanCustomizations]
class: mailman_customizations.hooks.MailmanCustomizations
enabled: no
component_package: mailman_customizations
In ^ case, the "name" of the plugin, "MailmanCustomizations" in this case, doesn't matter and can be anything and mailman will use "component_package" as the base module to look for components.
-- thanks, Abhilash Raj (maxking)