Make pyproject.toml PEP 621 compliant

[simontegelid]

The issue is (had issues with building this with buildroot), which requires this to be correct:

$ validate-pyproject pyproject.toml                          
Invalid file: pyproject.toml
[ERROR] `project.license` must be valid exactly by one definition (2 matches found):

    - keys:
        'file': {type: string}
      required: ['file']
    - keys:
        'text': {type: string}
      required: ['text']

For more info: https://peps.python.org/pep-0621/#license

After this change:

$ validate-pyproject pyproject.toml
Valid file: pyproject.toml

For the record:

$ validate-pyproject --version     
validate_pyproject 0.10.1

[Kludex]

@ofek do you have instructions here?

[iudeen]

Based on the Hatch Documentation the existing one seems fine.
Also check https://peps.python.org/pep-0639/#add-string-value-to-license-key

PEP 639 supersedes PEP 621?

[simontegelid]

PEP 621 is a bit vague in that "The table may have one of two keys" (just "may") and at the same time "A practical string value for the license key has been purposefully left out to allow for a future PEP to specify support for SPDX expressions". Seems like PEP 639 deprecate license sub keys https://peps.python.org/pep-0639/#deprecate-license-key-table-subkeys (had missed this PEP until now). What a mess. So, maybe it's an error to merge this after all.

[Kludex]

So... Do we close this?

[ofek]

related: psf/black#3326 (comment)

[iudeen]

Is it only the moon launch that's delaying the approval of PEP639?😂

[ofek]

yup lollll

[Kludex]

So, maybe it's an error to merge this after all.

Ok. Thanks. 🙏