Better error logging if a plugin refuses to load #3276
Merged
Conversation
This file contains 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
avaris
reviewed
Jan 15, 2024
avaris
reviewed
Jan 15, 2024
justinmayer
approved these changes
Jan 29, 2024
There was a problem hiding this comment.
Many thanks to @MinchinWeb for the enhancement and to @avaris for reviewing 💯
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Further to #3257, this will print the proper line number if a plugin fails to load, and will print the stacktrace, if pelican is run with
--debug.Useful when you're first trying to get a plugin to load, or have issue when Pelican first imports/loads the plugin.