Use correct variable for scope in i2c i/o errors #118
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
The i2c i/o error code currently tried to use `e` which only exists in the scope of the earlier `except` block. The correct scope variable is `error` which `e` is assigned out to. The existing code will yield UnboundLocalError "local variable 'e' referenced before assignment" instead of passing the original error.
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.
The i2c i/o error code currently tried to use
ewhich only exists in the scope of the earlierexceptblock. The correct scope variable iserrorwhicheis assigned out to.The existing code will yield UnboundLocalError "local variable 'e' referenced before assignment" instead of passing the original error.