You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before license expressions, the license table was allowed to contain a text key. That never got implemented even though the docs list it as supported. Map license.text to the License core metadata field.
Thanks, but I actually took it back out deliberately. It was never clear to me whether the project.license.text field was meant to contain a license name or the full text of the license, and I didn't want to mess up the metadata with the full text, especially since it wasn't really used for anything. Before the license expressions, the classifiers were the best way to add vaguely structured info about licenses. And it seems a bit weird to start adding that in just when it's deprecated.
Sorry not to be clearer about that and leave you redoing the change!
It was never clear to me whether the project.license.text field was meant to contain a license name or the full text of the license, and I didn't want to mess up the metadata with the full text, especially since it wasn't really used for anything.
Yeah, I agree that it was kind of confusing. The best way I've seen it used is actually with a SPDX license identifier itself, before just project.license was allowed / supported. Since the License metadata field is actually displayed on PyPI as well, that was quite useful.
Not really necessary now that license expressions will be officially supported.
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
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.
Before license expressions, the license table was allowed to contain a
textkey. That never got implemented even though the docs list it as supported. Maplicense.textto theLicensecore metadata field.flit/doc/pyproject_toml.rst
Lines 98 to 101 in 2818f41
It seems this was accidentally removed in f08bb9f