BF: use inspect.getfile to check path of plugin entry points#6660
Merged
Conversation
peircej
added
the
🐞 bug
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix a bug that got introduced in #6610 - I forgot to consider the use of entry-points for classes in addition to importing modules.
Classes require a different way from modules for checking the file path, as previously done correctly by @TEParsons using
inspect.getfile(), which #6610 incorrectly removed. This BF adds that back.tryblock afterep.load(), so that if a plugin fails to load, it won't crash the entire script.