Allow METADATA
file to contain UTF-8 chars
#489
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.
setuptools
produces UTF-8PKG-INFO
files. However, after processed bywheel
, some serialization problems show up in theMETADATA
file (see pypa/setuptools#3663 (comment))This PR attempts to allow UTF-8 in
METADATA
1 produced by wheel.Closes #488.
Footnotes
Initially, I was not 100% sure if the issue was related to standardization. PyPA specs do mention a bunch of old RFCs, but they are also clear state that "strings must be serialised using the UTF-8 encoding". Flit adopts the UTF-8 approach. ↩