Licensing metadata is very long

[hyandell]

Hi platformdirs folk,

I noticed on https://pypi.org/project/platformdirs/ that the licensing metadata section of the package is including the full license. I'm not sure if that was intended; it flagged for me on a script that was expecting something more like "MIT" or "MIT License".

[ofek]

Broke in #92 (see https://pypi.org/project/platformdirs/2.5.2/)

Hatchling produces a less verbose license section on PyPI because until they support PEP 639 the rendering is not what one may think. It's actually "License: {license_classifier.split(' :: ')[-1]} ({license['text']})"

[gaborbernat]

@ofek so how do I fix it? 😆

[ofek]

go back to license = "MIT"

[gaborbernat]

      ValueError: invalid pyproject.toml config: `project.license`.
      configuration 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']

seems pypy setup triggers setuptools that runs its check automatically and fails with this 🤦 once making your suggested change. Ah setuptools what a mess!

[ofek]

when is setuptools triggered? pypy works fine in other ci

[gaborbernat]

See https://github.com/platformdirs/platformdirs/actions/runs/3417581616/jobs/5688883308

[gaborbernat]

Fixed now