Skip to content
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

[3.13] GH-119496: accept UTF-8 BOM in .pth files (GH-119503) #119508

Merged
merged 1 commit into from
May 24, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented May 24, 2024

Out-File -Encoding utf8 and similar commands in Windows Powershell 5.1 emit
UTF-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

`Out-File -Encoding utf8` and similar commands in Windows Powershell 5.1 emit
UTF-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>
@ncoghlan ncoghlan enabled auto-merge (squash) May 24, 2024 14:37
@ncoghlan ncoghlan merged commit 217d57f into python:3.13 May 24, 2024
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants