PEP 639: Add documentation for Metadata 2.4, License-Expression and License-Field - #1595
Merged
Conversation
pradyunsg
approved these changes
Sep 15, 2024
Member
For deprecations, I'd say add For conflicts, I'd make a note of that in the body of the relevant fields (License / License-Expression, if my understanding of the fields is up to date). |
pradyunsg
approved these changes
Sep 16, 2024
brettcannon
approved these changes
Sep 18, 2024
Member
|
It looks like the link failure can be fixed with https://www.man7.org/linux/man-pages/man1/ldd.1.html . |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Starting to draft updates for PEP 693/Metadata 2.4.
I'm unsure how to capture the conflicts/deprecations.📚 Documentation preview 📚: https://python-packaging-user-guide--1595.org.readthedocs.build/en/1595/