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.

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

Jump to bottom

Require metadata to be serialised using UTF-8 #1046

Merged
merged 2 commits into from Feb 16, 2022
Merged

Require metadata to be serialised using UTF-8 #1046

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ca04bb
Require metadata to be serialised using UTF-8
pfmoore Feb 15, 2022
492cc5c
Merge branch 'main' into metadata_utf8
bhrutledge Feb 16, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions source/specifications/core-metadata.rst
View file
Open in desktop
Expand Up @@ -22,6 +22,9 @@ definition, the practical standard is set by what the standard library
:mod:`python:email.parser` module can parse using the
:data:`~.python:email.policy.compat32` policy.

Whenever metadata is serialised to a byte stream (for example, to save
to a file), strings must be serialised using the UTF-8 encoding.

Although :pep:`566` defined a way to transform metadata into a JSON-compatible
dictionary, this is not yet used as a standard interchange format. The need for
tools to work with years worth of existing packages makes it difficult to shift
Expand Down