[3.13] GH-119496: accept UTF-8 BOM in .pth files (GH-119503) #119508
Merged
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.
Out-File -Encoding utf8
and similar commands in Windows Powershell 5.1 emitUTF-8 with a BOM marker, which the regular
utf-8
codec decodes incorrectly.utf-8-sig
accepts a BOM, but also works correctly without one.This change also makes .pth files match the way Python source files are handled.
(cherry picked from commit bf5b646)
Co-authored-by: Alyssa Coghlan ncoghlan@gmail.com
Co-authored-by: Inada Naoki songofacandy@gmail.com