Show License-Expression if present in package metadata#13145
Show License-Expression if present in package metadata#13145
Conversation
|
Could you add a test for the new output? Thanks. |
|
Also, it looks like CI is failing as the |
cc804f4 to
09d36f0
Compare
I'm trying to, but have a hard time with simulating the data - do I have to create a package with new metadata in order to make pip "install" it and then assert the output? Any pointers will be appreciated. One more thing is, when pip itself moves to PEP 639 & setuptools supports it, this won't be true anymore: |
You might have to - there's some examples in |
|
FYI, CI should be working again, if you merge from main. |
09d36f0 to
246f323
Compare
With Core Metadata 2.4 a new field, License-Expression, has been added. If it's present, favor it over the deprecated (with PEP 639) legacy unstructured License field. Closes: pypa#13112
246f323 to
41c807c
Compare
|
Took me a while, but there are two tests added. |
|
Thanks for the contribution! |
|
Thank you indeed. Congratulations on the PEP! 🎉 |
With Core Metadata 2.4 a new field, License-Expression, has been added. If it's present, favor it over the deprecated (with PEP 639) legacy unstructured License field.
Closes: #13112