💅 Address all instances of BytesWarning
#648
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.
Things like byte-to-int comparisons and interpolation of bytes into str were present in the code base. This patch fixes that by making sure that the variables are always of compatible types in these cases.
❓ What kind of change does this PR introduce?
📋 What is the related issue number (starting with
#
)N/A
❓ What is the current behavior? (You can also link to an open issue here)
Currently, a
BytesWarning
is emitted. Mostly in tests, but there's one place where it's happening in the HTTP parser too.❓ What is the new behavior (if this is a feature change)?
BytesWarning
no more!📋 Other information:
N/A
📋 Contribution checklist:
(If you're a first-timer, check out
this guide on making great pull requests)
the changes have been approved
and description in grammatically correct, complete sentences
This change is