-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-77749: Fix inconsistent behavior of non-ascii handling in EmailPolicy.fold #6986
gh-77749: Fix inconsistent behavior of non-ascii handling in EmailPolicy.fold #6986
Conversation
This PR is stale because it has been open for 30 days with no activity. |
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 resolved conflicts, added a NEWS entry and optimized the code.
It LGTM now.
Thanks @Licht-T for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
…ailPolicy.fold() (pythonGH-6986) It now always encodes non-ASCII characters in headers if utf8 is false. (cherry picked from commit 504334c) Co-authored-by: Rito Takeuchi <licht-t@outlook.jp> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…ailPolicy.fold() (pythonGH-6986) It now always encodes non-ASCII characters in headers if utf8 is false. (cherry picked from commit 504334c) Co-authored-by: Rito Takeuchi <licht-t@outlook.jp> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
GH-114606 is a backport of this pull request to the 3.12 branch. |
GH-114607 is a backport of this pull request to the 3.11 branch. |
Thank you for your contribution, @Licht-T, and sorry for the delay. |
…ailPolicy.fold() (pythonGH-6986) It now always encodes non-ASCII characters in headers if utf8 is false. Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…ailPolicy.fold() (pythonGH-6986) It now always encodes non-ASCII characters in headers if utf8 is false. Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
This fixes bpo-33568.
https://bugs.python.org/issue33568