beetbox / beetbox/beets

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

Open
#5,740 0 comments 1 reaction 1 assignee Claimed by @wisp3rwind View on GitHub
discussion
Dominant language
Python
Stars
15.7k
Forks
2.1k
Avg merge
4d 21h
Merged PRs (30d)
31

Description

This came up in https://github.com/beetbox/beets/pull/5739#discussion_r2050456386:

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.