Add support for Metadata 2.2 #2293
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This works for everything except local, archived distributions. Want to do one refactor on |
charliermarsh
force-pushed
the
charlie/metadata-2.2
branch
2 times, most recently
from
12770b1 to
acc8f4b
Compare
charliermarsh
force-pushed
the
charlie/metadata-2.2
branch
from
acc8f4b to
3d27f19
Compare
charliermarsh
added
the
enhancement
charliermarsh
force-pushed
the
charlie/metadata-2.2
branch
2 times, most recently
from
258283f to
c59e8f5
Compare
charliermarsh
force-pushed
the
charlie/metadata-2.2
branch
from
c59e8f5 to
5d96339
Compare
charliermarsh
force-pushed
the
charlie/metadata-2.2
branch
from
288a2a9 to
4605e44
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
PyPI now supports Metadata 2.2, which means distributions with Metadata 2.2-compliant metadata will start to appear. The upside is that if a source distribution includes a
PKG-INFOfile with (1) a metadata version of 2.2 or greater, and (2) no dynamic fields (at least, of the fields we rely on), we can read the metadata from thePKG-INFOfile directly rather than running any of the PEP 517 build hooks.Closes #2009.