diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2024-05-24 14:52:20 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-24 14:52:20 (GMT) |
| commit | 217d57fc3c9a8ec45dfccd3aab9a05dbf6656da0 (patch) | |
| tree | 74073c35724e69376d17a9cfb9cbde72269ea086 /Python/pystrhex.c | |
| parent | 0bab0b3a53da735838720f96f3d3bf86ca6ba125 (diff) | |
| download | cpython-217d57fc3c9a8ec45dfccd3aab9a05dbf6656da0.zip cpython-217d57fc3c9a8ec45dfccd3aab9a05dbf6656da0.tar.gz cpython-217d57fc3c9a8ec45dfccd3aab9a05dbf6656da0.tar.bz2 | |
[3.13] GH-119496: accept UTF-8 BOM in .pth files (GH-119508)
`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 bf5b6467f8cc06759f3396ab1a8ad64fe7d1db2e)
Co-authored-by: Alyssa Coghlan <ncoghlan@gmail.com>
Co-authored-by: Inada Naoki <songofacandy@gmail.com>
Diffstat (limited to 'Python/pystrhex.c')
0 files changed, 0 insertions, 0 deletions