Skip to content

PEP 680: Further explain why files are read as binary #2281

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.

Sign up for GitHub

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

Merged
encukou merged 2 commits into from
Jan 27, 2022
Merged

PEP 680: Further explain why files are read as binary #2281

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce3d680
PEP 680: further explain binary files
Jan 26, 2022
d1df0be
code review
Jan 26, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions pep-0680.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,8 +289,9 @@ be worked around in user code, or by using a third-party library.

The proposed API takes a binary file, while ``toml.load`` takes a text file and
``json.load`` takes either. Using a binary file allows us to ensure UTF-8 is
the encoding used, and avoid incorrectly parsing single carriage returns as
valid TOML due to universal newlines in text mode.
the encoding used (ensuring correct parsing on platforms with other default
encodings, such as Windows), and avoid incorrectly parsing files containing
single carriage returns as valid TOML due to universal newlines in text mode.


Type accepted as the first argument of ``tomllib.loads``
Expand Down