Support PEP 639 license metadata once that PEP is accepted
See original GitHub issueThis project has a license
defined under the [project]
table in pyproject.toml
:
https://github.com/heroku/sf-functions-python/blob/a7541831525ae1850ae2c8511d2b0c8f94597a53/pyproject.toml#L10
However, pyroma 4.1 on macOS using Python 3.11.0 reports that no license was specified:
$ pyroma .
------------------------------
Checking .
Getting metadata for wheel...
Found salesforce-functions
------------------------------
...
Your package does neither have a license field nor any license classifiers.
Issue Analytics
- State:
- Created 9 months ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
PEP 639 – Improving License Clarity with Better Package ...
This PEP defines a specification for how licenses are documented in the core metadata, with license expression strings using SPDX ...
Read more >Warn about redundant license field if classifier is present #465
Once PEP 639 is accepted, we'll deprecate both the license classifiers as well as the regular table-based license fields.
Read more >Metadata - Hatch
Project metadata is stored in a pyproject.toml file located at the root of a project's tree and is based entirely on PEP 621....
Read more >Tree - rpms/pyproject-rpm-macros - Fedora Package Sources
general Python projects that use the [PEP 517] `pyproject.toml` file (which ... build system must support the [prepare-metadata-for-build-wheel hook].
Read more >Setuptools and PEP 621 - ini2toml
This might change in the future if PEP 639 is accepted. Meanwhile, metadata.license_files is translated to tool.setuptools.license-files . Please note these ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s leave it open.
Up to @regebro