PyPI: Very long license badge

[maximlt]

Are you experiencing an issue with...

shields.io

🐞 Description

Per PEP 621 a Python package can be distributed with a license metadata field set to either file: link_to_license_file or text: some_license_text.

Packages that set file instead of text can end up with very long content. This seems to be valid, as demonstrated by the long version content you can see on Bokeh's PyPI page, this project setting file indeed.

🔗 Link to the badge

This leads to a very long badge :)
https://img.shields.io/pypi/l/bokeh

💡 Possible Solution

Shouldn't the badges be built from the License classifier instead of the core license metadata?

[chris48s]

This is an amusing example :)

One issue here is that there is nothing in the JSON response from PyPI (e.g: https://pypi.org/pypi/bokeh/json ) that explicitly says whether the contents of license is file or text so we'll have to use some judgement. I'll get a PR up shortly..

[maximlt]

For what it's worth this issue triggered a longer discussion on DPO.