avoid pylint crash on ill-formatted template strings #1
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.
We use pylint to evaluate student submission on an electronic learning environments. Pylint crashed while evaluating this submitted code snippet:
Clearly the template string is ill-structured (dot and colon should be swapped) and pylint should annotate this as such (not crash). Here's the stack trace:
I have caught the exception in the
parse_format_method_string
and raised anutils.IncompleteFormatString()
exception instead in this pull request. This should avoid the pylint crash. Someone should check if the error handling results in the correct pylint annotation, or to see if the problem could be handled earlier (because format string is not valid according to PEP 3101).