Skip to content

plugins: Should beets exit if plugins are not found or fail to load? #5740

Open
@wisp3rwind

Description

@wisp3rwind

This came up in #5739 (comment):

Currently, we're not really consistent, for example aborting if plugin init fails, but not if the plugin has syntax errors.

In my opionion, we should simply always exit with a human-readable error, since this has the potential to mess up imports (for example due to missing stages) in hard-to-fix ways. But as shown by the linked discussion, there might be different opinions on how beets should behave.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions