sopel-plugins
CLI doesn't show broken plugin source
#2113
Labels
Milestone
sopel-plugins
CLI doesn't show broken plugin source
#2113
One of the main utilities our
sopel-plugins
CLI tool provides is showing what plugins are available, and where they come from (a file, a folder, a package). It works great for plugins that can load as valid Python modules, but shows only "unknown" for the source location if loading generates an error of any kind—meaning there is a mistake in the plugin code:Ideally, even if loading fails,
sopel-plugins
would be able to at least show the type and source of a broken plugin so the user can easily go fix the problem and/or report it to the author.This isn't just my random idea; it came from a long troubleshooting session on IRC yesterday, followed by @Exirel's later reflection that
sopel-plugins list
helped confirm that there existed a problem, but not where.Note: My
broken.py
plugin file was literally one line, very easy to test.bot.say("This can't ever work.")
The text was updated successfully, but these errors were encountered: