Handle pandoc logging returning two unknown log levels #272
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.
This is a follow up to #271, which deals with the case where pandoc produces more than one logging message with non-standard levels, followed by another log message. For example, the following pandoc output still produced a
KeyError
:This PR updates the
_classify_pandoc_logging
function and thetest_classify_pandoc_logging_invalid_level
test to correctly handle this case.I have also updated the
level_map
dictionary which converts the pandoc levels to python codes, so that it only contains levels formally used by pandoc.Fixes #269