Repository navigation
gh-62259: Add support of multi-byte encodings in the XML parser - #149860
Merged
serhiy-storchaka merged 5 commits intoMay 26, 2026
Merged
serhiy-storchaka merged 5 commits into
serhiy-storchaka merged 5 commits into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Supported encodings: "cp932", "cp949", "cp950", "Big5","EUC-JP", "GB2312", "GBK", "johab", and "Shift_JIS". Partially supported encodings (only BMP characters): "Big5-HKSCS", "EUC_JIS-2004", "EUC_JISX0213", "Shift_JIS-2004", "Shift_JISX0213", "utf-8-sig" and non-standard aliases like "UTF8" (without hyphen). The parser now raises ValueError for known unsupported multi-byte encodings such us "ISO-2022-JP" or "raw-unicode-escape" instead of failing later, when encounter non-ASCII data.
Copy link
Copy Markdown
Documentation build overview41 files changed · + 1 added · ± 40 modified + Added ± Modified |
Sorry, something went wrong.
malemburg
approved these changes
May 15, 2026
malemburg
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
LGTM.
The only detail that is missing is the documentation update. This still reads "UTF-8, UTF-16, ISO-8859-1 (Latin1), and ASCII" which already appears to be out of date.
Sorry, something went wrong.
Comment thread
Doc/library/pyexpat.rst
Outdated
Comment thread
Doc/library/pyexpat.rst
Outdated
| *encoding* [1]_ is given it will override the implicit or explicit encoding of the | ||
| document. | ||
| must be a string naming the encoding used by the XML data. | ||
| Expat natively understands and processes UTF-8, UTF-16, UTF-16BE, UTF-16LE, |
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
I think this should be an .. impl-detail (I don't remember the exact name)?
Sorry, something went wrong.
Comment thread
Doc/whatsnew/3.16.rst
Outdated
Comment thread
Misc/NEWS.d/next/Library/2026-05-14-17-01-19.gh-issue-62259.ytlFD5.rst
Outdated
Co-authored-by: Stan Ulbrych <stan@python.org>
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
Reviewers
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.
Supported encodings: "cp932", "cp949", "cp950", "Big5","EUC-JP", "GB2312", "GBK", "johab", and "Shift_JIS".
Partially supported encodings (only BMP characters): "Big5-HKSCS", "EUC_JIS-2004", "EUC_JISX0213", "Shift_JIS-2004", "Shift_JISX0213", "utf-8-sig" and non-standard aliases like "UTF8" (without hyphen).
The parser now raises ValueError for known unsupported multi-byte encodings such us "ISO-2022-JP" or "raw-unicode-escape" instead of failing later, when encounter non-ASCII data.