Merged
Conversation
Reconfigure stdout and stderr to use UTF-8 encoding to fix Windows GBK pipe issue.
There was a problem hiding this comment.
Pull request overview
This PR fixes a Windows-specific encoding issue (#33) where piping output through Windows terminals using GBK encoding causes errors when outputting UTF-8 characters (e.g., Chinese text or emoji).
Changes:
- Reconfigures
sys.stdoutandsys.stderrto use UTF-8 encoding at the start ofmain()to prevent GBK encoding errors on Windows.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
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.
Reconfigure stdout and stderr to use UTF-8 encoding to fix Windows GBK pipe issue.