fix: raise the intended ValueError for non-ascii hex strings - #67
Draft
nikolauspschuetz wants to merge 1 commit into
Draft
fix: raise the intended ValueError for non-ascii hex strings#67nikolauspschuetz wants to merge 1 commit into
nikolauspschuetz wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
hexstr_to_bytesguardspadded_hex.encode("ascii")withexcept UnicodeDecodeError, butstr.encoderaisesUnicodeEncodeError— so the handler never runs and a non-ascii hex string surfaces the raw codec error instead of the intendedValueError:Correcting the caught type raises the message the handler was written for —
ValueError: hex string 0é may only contain [0-9a-fA-F] characters. Valid hex is unaffected. Added a regression test (there was none for non-ascii input).