Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this technically be
?
Seriously, just:
... we don't need Python2 compatibility any more (
pymavlinkis no longer Python2-compliant so no new installs are going to work on Py2 anyway).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think
unicodeexists in python3, at least by default. My understanding is that it's a python2 forward-compat alias for a python3 str.I also think code that has historically supported python2 may still be passing bytes around as strings, so that's why the
pastmodule uses(bytes, str)instead of juststr. If that's not the case here for dronekit, then I agree it's simpler to just usestr.