This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
except ParseError: --> except ParseError as e: #1177
Merged
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.
Make the same fix in four different files where we are catching a ParseError and then re-raising it. In the except statement, we need to capture the exception into the variable in e so that we can re-raise it in the lines immediately following. Without this change, we would raise a NameError instead of the intended exception.
Discovered via flake8 testing of https://github.com/hyperledger/sawtooth-core on Python 3.6.3
$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
Signed-off-by: cclauss cclauss@bluewin.ch