add encoding comment in nvofbf.py to fix SyntaxError when using Python 2#4163
Merged
Micket merged 1 commit intoeasybuilders:developfrom Jan 5, 2023
Merged
add encoding comment in nvofbf.py to fix SyntaxError when using Python 2#4163Micket merged 1 commit intoeasybuilders:developfrom
Micket merged 1 commit intoeasybuilders:developfrom
Conversation
8aa07fe to
02d2223
Compare
Member
Author
|
I ran some debug CI workflows to try and understand why the encoding issue wasn't triggered in the CI environment, but I'm still not sure. Even when setting both I wouldn't block this PR over this though, we can always undo this fix if we want to keep hunting for the reason why this bug isn't being triggered in CI... |
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.
(follow-up for #4157)
Without this,
eb --list-toolchainsis broken when running on top of Python 2 (and probably more):What's weird is that the test suite didn't catch this. It should have been caught by the
test__list_toolchainstest, but somehow that's not the case for the tests being run in GitHub Actions...(hat tip @migueldiascosta)