leifdreizler commented on PR #53828:
URL: https://github.com/apache/airflow/pull/53828#issuecomment-3145418657

   **Core Metadata**
   What is found in the `.whl` file on PyPI
   
   - `License` (deprecated)
   - `License-Expression` (added)
   - `License-File` (added)
   
   **Project Metadata**
   What is found in the repo's manifest file
   
   - license key table, e.g. `license = {text = "BSD-3-Clause"}` or `license = 
{file = "LICENSE"}` (deprecated)
   - `license` string (added)
   - `license-files` (added)
   
   Examples of deprecated `license` with subkeys:
   - Version 3.0.1 of flask demonstrates the [file 
subkey](https://github.com/pallets/flask/blob/3.0.1/pyproject.toml#L6)
   - Django uses the old [text 
subkey](https://github.com/django/django/blob/main/pyproject.toml#L19)
   
   The latest version of flask uses the `license` string and `license-files` 
keys [as seen 
here](https://github.com/pallets/flask/blob/3.1.1/pyproject.toml#L6-L7)
   
   If you download and unzip the `.whl` file for the latest version of [Flask 
from PyPI](https://pypi.org/project/Flask/#files), you'll see the following 
metadata:
   
   ```
   Metadata-Version: 2.4
   Name: Flask
   Version: 3.1.1
   Summary: A simple framework for building complex web applications.
   Maintainer-email: Pallets <[email protected]>
   Requires-Python: >=3.9
   Description-Content-Type: text/markdown
   License-Expression: BSD-3-Clause
   License-File: LICENSE.txt
   ```
   
   which matches the [PyPI API response for 
Flask](https://pypi.org/pypi/flask/json). As you can see, the Project Metadata 
is creating the correct Core Metadata. `license` is null and 
`license_expression` and `license_files` are correctly populated.
   
   ```
       "license": null,
       "license_expression": "BSD-3-Clause",
       "license_files": [
         "LICENSE.txt"
       ],
   ```
   
   I believe this will work for y'all as well. What do you think?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to