[pypi] Improve formatting of trove-based licenses #3265
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
paulmelnikow
added
the
service-badge
|
|
Semi-related, I noticed that the color schemes applied on license badges vary between license services as well. Is that intentional or worth potentially trying to make them consistent at some point in the future? |
|
Yes! There's some discussion of that at #2026. |
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.
Currently the trove-based license classifiers generate different formatting than the legacy license classifiers. This brings them into alignment.
Production:
This PR:
Think this is a good improvement; more consistent with most other badges, and will look better on readmes (see https:/lace/vg for an example).