Add FAQ entry about UnicodeEncodeError on Windows - #3778
Merged
Conversation
kdeldycke
added
windows
kdeldycke
force-pushed
the
unicode-windows-faq
branch
from
August 19, 2026 04:48
b86024c to
fc3273a
Compare
davidism
approved these changes
Aug 19, 2026
ddelange
reviewed
Aug 19, 2026
kdeldycke
force-pushed
the
unicode-windows-faq
branch
from
August 19, 2026 16:24
fc3273a to
e1021e3
Compare
ddelange
reviewed
Aug 19, 2026
kdeldycke
force-pushed
the
unicode-windows-faq
branch
from
August 19, 2026 16:36
50fdaa5 to
2e36e24
Compare
Member
|
@kdeldycke left a few typo comments |
kdeldycke
force-pushed
the
unicode-windows-faq
branch
from
August 20, 2026 05:00
2e36e24 to
131c86a
Compare
Collaborator
Author
Ah yes good catch. Fixed! :) |
Rowlando13
approved these changes
Aug 20, 2026
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
4 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.
This add a FAQ entry about a long requested issue with unicode errors on Windows.
I explained clearly why this is not a bug for Click to solve and is a system configuration.
I've been using that for 4 years in production and it just works: kdeldycke/meta-package-manager@51f392a#diff-95557d53bf91069e59d82b9d8fcfaf52ec84a762858983edd5ef3c9b3e4c8191R337-R342
Closes #2121