Repository navigation
MNT: Use UTF-8 string in macosx backend - #23558
Merged
jklymak merged 1 commit intoAug 5, 2022
Merged
jklymak merged 1 commit into
jklymak merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Python 3 always passes UTF8 encoded strings, so just use that directly instead of specifying the encoding later.
QuLogic
approved these changes
Aug 5, 2022
jklymak
approved these changes
Aug 5, 2022
6 tasks
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
3 participants
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.
PR Summary
Python 3 always passes UTF8 encoded strings, so just use that directly
instead of specifying the encoding later.
replaces #21756 because the autorelease semantics was already changed in another PR.
PR Checklist
Tests and Styling
Documentation